Description

CatarinaGamboa

opened on Dec 10, 2025

Issue body actions

return is a statement, and it's strange to have it as a variable to represent the return value.
Therefore, we could change it for result. But since result can be an actual variable that represents something other than the return value we, we can try using $result.

This would mean a small change in the grammar, probably, and a change in replacing the return value.
Ps: the _ should still work in any case

Example Before:

@Refinement("return > 0") 
int test2 (){
    return 10;
}

Example After:

@Refinement("$result > 0") 
int test2 (){
    return 10;
}

Activity

1. CatarinaGamboa

   added

   good first issueGood for newcomersGood for newcomers

   enhancementNew feature or requestNew feature or request

   on Dec 10, 2025
2. alcides commented on Dec 10, 2025

   

   alcides

   on Dec 10, 2025

   Collaborator

   More actions

   I support this change. I never liked return in the refinement for that reason.
3. rajshivu commented on Feb 9, 2026

   

   rajshivu

   on Feb 9, 2026

   More actions

   Hi 👋 I’d like to work on this issue and implement the $result replacement as suggested.
   I’ll make sure _ continues to work as well.
   Please let me know if there’s anything specific you’d like me to watch out for.
4. rajshivu commented on Feb 9, 2026

   

   rajshivu

   on Feb 9, 2026

   More actions

   Hi,
   I’ve implemented a fix for the refinement variable mapping issue ('_' and 'return' → $result). I’ve tested it manually, and the branch is ready.
   I’ve created a Pull Request here: #145
   Please take a look when you get a chance. Let me know if any further changes are needed.
5. rcosta358

   linked a pull request that will close this issueAdd `#result` for Return Refinements #145on Feb 15, 2026
6. alcides commented on Oct 15, 2026

   

   alcides

   on Oct 15, 2026

   Collaborator

   More actions

   Does this still make sense @CatarinaGamboa?

Issue actions