Comment by ~sebsite on ~sircmpwn/hare
Dmitry Matveyev referenced this ticket in commit 0429880.
REPORTED
RESOLVED IMPLEMENTEDComment by ~sebsite on ~sircmpwn/hare
REPORTED
RESOLVED IMPLEMENTEDeasy added by ~sebsite on ~sircmpwn/hare
spec added by ~sebsite on ~sircmpwn/hare
Ticket created by ~sebsite on ~sircmpwn/hare
938ac7b adds attributes as tokens, however, it still doesn't match the behavior of harec. Since
@
is only allowed within a token when it exactly matches one of the listed attributes, it follows that any trailing characters aren't part of the token, and should be separated. Thus, according to the spec, the following code is valid:@testfn foo() void = void; let @threadlocalbar = 0;
Comment by ~sebsite on ~sircmpwn/hare
We may also want to use -fsanitize=undefined
easy added by ~sebsite on ~sircmpwn/hare
Comment by ~sebsite on ~sircmpwn/hare
This isn't an issue with the syntax summary appendix, this is an issue with the nonterminaldefs themselves. Most lines for nonterminals end with \\, but some don't (like in lexical analysis, and ones that are immediately followed by \end{grammar}). So we should go through the spec and make sure we're consistently using \\ everywhere we should be.
Comment by ~sebsite on ~sircmpwn/hare
Allowing intermediate results to be
(null | str)
without just allowingnull
types on their own in general would be, very weird, and probably not a good idea. I think we should either just makenull
a regular type, or say that this is intended behavior.
Comment by ~sebsite on ~sircmpwn/hare
If we make
null
an actual representable type then we can just say that at the end of type reduction, if there's one pointer and a null type, it turns into a nullable pointer, but otherwise the null type is still allowed.