-
Notifications
You must be signed in to change notification settings - Fork 18
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
When comment is not enough #63
Comments
The syntax is slightly different:
|
That version is still missing a set of parens:
Adding the pair then generates a function call:
The intended output is the (somewhat weird) gcc syntax:
|
Support for new command
yields:
works also with multiple arguments: |
It's now possible to disable the line break in comments with:
allowing easy workarounds:
|
It seems we forgot about a very unfortunate operator:
I think parsing this one will be really hard, so I'm open for alternatives, one would be just keeping
I'm basically re-opening this to have it acknowledged. :) |
What about adding an inverted reader to |foo|? |
How bad do you think this would mess up regular code? Think of SBCL's |
Proposal: simply use |
I want to write this code:
However, neither of the following two work. The former because the function-call gets messed up (which, I think, is ok), the latter because of c-compatible renaming (which, I think, we want to have in the general case).
The result is as follows
As usual with unusual cases,
comment
comes in handy:But starts a new line:
@lispbub Maybe we can just add an option to
comment
to not trigger a newline?The text was updated successfully, but these errors were encountered: