Skip to content

Don't assume optimization when for recursive function contracts.#866

Draft
samth wants to merge 1 commit intoracket:masterfrom
samth:fix-unopt-contract
Draft

Don't assume optimization when for recursive function contracts.#866
samth wants to merge 1 commit intoracket:masterfrom
samth:fix-unopt-contract

Conversation

@samth
Copy link
Copy Markdown
Member

@samth samth commented Oct 10, 2019

Currently TR generates contracts that assume parts will be optimized
away by static contract optimization. If that doesn't happen, the
resulting recursive contracts are invalid.

For @camoy. Not intended for merging or general use.

Related to #858.

Currently TR generates contracts that assume parts will be optimized
away by static contract optimization. If that doesn't happen, the
resulting recursive contracts are invalid.

For @camoy. Not intended for merging or general use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant