Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect recursive function warnings, with cycles #720

Closed
nickbattle opened this issue Apr 28, 2020 · 1 comment
Closed

Incorrect recursive function warnings, with cycles #720

nickbattle opened this issue Apr 28, 2020 · 1 comment
Assignees
Labels
bug Incorrect behaviour of the tool language Issues in parser, TC, interpreter, POG or CG Mergable A fix is available on a branch to merge for release
Milestone

Comments

@nickbattle
Copy link
Contributor

There is a problem with the reporting of "missing measures" for recursive functions in 2.7.4.

If a function is part of a mutually recursive cycle, and it calls other functions that are not part of the cycle (but not itself), it will have a warning "Recursive function has no measure", as well as "Mutually recursive cycle has no measure" and the cycles. It ought really only to have the cycles warning, since it is not (simply) recursive.

@nickbattle nickbattle added bug Incorrect behaviour of the tool language Issues in parser, TC, interpreter, POG or CG labels Apr 28, 2020
@nickbattle nickbattle self-assigned this Apr 28, 2020
@nickbattle nickbattle added the Mergable A fix is available on a branch to merge for release label Apr 28, 2020
@nickbattle
Copy link
Contributor Author

Fix now available in ncb/development.

@idhugoid idhugoid added this to the v3.0.0 milestone Aug 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Incorrect behaviour of the tool language Issues in parser, TC, interpreter, POG or CG Mergable A fix is available on a branch to merge for release
Projects
None yet
Development

No branches or pull requests

2 participants