Alberto Goffi

Missing translation of @return comments about "empty" return value

2

Toradocu is not able to translate `@return` comments about the emptiness of the return values. Some examples: ``` Empty @return condition. Comment: an empty Bag Expected condition: true?result.isEmpty()==true Actual condition:...

Once Toradocu derived constructor/method specifications, Toradocu should report: - [ ] **Conflicts**: two specs cannot have the same guard. - [ ] **Multiple outcomes**: two specs cannot have guards that...

Add purity analysis to use only pure methods in generated specifications (and therefore oracles).

Currently the output of Toradocu does not help to understand what it is going on internally. We have a `--debug` option, but it is not used. We should output informative...

Missing translation of @return comments about "empty" or null argument

1

Toradocu does not translate `@return` comments that involve properties of the arguments. Some examples: ``` Empty @return condition. Comment: true if empty or null Expected condition: args[0].isEmpty()||args[0]==null?result==true Actual condition: ```...

**Input**: "`@param` predicates the the predicates to check, cloned, not null" **Expected output**: `(args[0]==null) == false` **Actual output**: `(args[0]==null) == false || (target.getPredicates()==null) == false` From the comment Toradocu extracts...

Toradocu generates method/constructor specifications using `args[]` pattern to refer to parameters. This is due to an implementation detail that should not influence the generated specifications. Specifications should be generated using...