I have not updated the "last change" header at the top of the syntax file, as the upstream repository was last modified on February 1st still. I'm not sure if the same date should be used here, or if it would be better to list the date of this downstream commit instead.
https://github.com/vim/vim/pull/19398
(1 file)
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Is @offset no longer a hare keyword?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
That's right. It was removed and replaced with _: typename in struct/union declarations to describe the offset amount.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Okay and should we keep this enabled for users still using older versions of Hare? Or do you think it is okay to drop it directly?
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I personally don't believe it makes sense to keep it. Hare is still quite a small language, and the majority of users are closely following (or involved with) its development and using the latest master, while the remainder are using the latest release. Additionally, @offset was not a very commonly used attribute in the first place, so I think the overall impact is quite low.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I have not updated the "last change" header at the top of the syntax file, as the upstream repository was last modified on February 1st still. I'm not sure if the same date should be used here, or if it would be better to list the date of this downstream commit instead.
I use the upstream change dates.
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()