Bare methods and bare lambdas (RFC 34) #1858
Conversation
Praetonus
added
the
changelog - added
|
Before we merge this, I want to note the documentation and other "how we teach this changes" that we should have ready at the same time: |
| } | ||
|
|
||
| member = ast_sibling(member); | ||
| } |
There was a problem hiding this comment.
Shouldn't there only be a single member in a bare type - the bare method?
Under what circumstances might a bare type have any fields or non-bare methods?
There was a problem hiding this comment.
There is the constructor.
|
I've added examples and opened a tutorial PR. |
| { | ||
| i = 1; | ||
| offset = 0; | ||
| } |
There was a problem hiding this comment.
CI is complaining about this - either need to surround this block with #if PONY_LLVM >= 309, or add a (void)offset; statement to prevent compiler warnings/errors about this variable not being used when the PONY_LLVM >= 309 condition on the later line is not met.
These new language constructs can be used in FFI interoperation with C libraries that use function pointers as callbacks. Closes ponylang#1690.
|
Awesome work! |
This was broken as a side effect the placement of a check introduced in #1858, and was fixed by just changing the order of the checks so that we don't expect to be in a method body frame if we are in a default argument frame.
This was broken as a side effect the placement of a check introduced in #1858, and was fixed by just changing the order of the checks so that we don't expect to be in a method body frame if we are in a default argument frame.
These new language constructs can be used in FFI interoperation with C libraries that use function pointers as callbacks.
Closes #1690.