We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems Kawa sometimes skips internally-defined procedures. Per #33, we do enable full-tailcall so I think there is some pitfall on that option..
For example,
(define (blockcomment-depth++) (%blockcomment-depth-add! 1)) (define (blockcomment-depth--) (%blockcomment-depth-add! -1))
blockcomment-depth++ would be skipped but blockcomment-depth-- won't. blockcomment-depth-- always have blockcomment-depth-zero? followed.
blockcomment-depth++
blockcomment-depth--
blockcomment-depth-zero?
The text was updated successfully, but these errors were encountered:
WARed: 51b1d57 Added --no-inline.
--no-inline
Sorry, something went wrong.
repro: https://gist.github.com/okuoku/d5cba6f31b781db911aa It seems backend bug. ISSUETrack.
Removed WAR: 7bebb26
Upstream fixed the problem. CLOSE.
ref: https://sourceware.org/ml/kawa/2016-q1/msg00014.html
No branches or pull requests
It seems Kawa sometimes skips internally-defined procedures. Per #33, we do enable full-tailcall so I think there is some pitfall on that option..
For example,
blockcomment-depth++
would be skipped butblockcomment-depth--
won't.blockcomment-depth--
always haveblockcomment-depth-zero?
followed.The text was updated successfully, but these errors were encountered: