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
antlr4-go out-of-date #4552
Comments
The entire antlr4 is actually out-of-date, no big improvements are planned. |
Basically there are two changes in the dev repo that I need to bring over
to the release repo and then re-tag.
You should use ANTLR-go repo.
…On Sun, Mar 10, 2024 at 04:13 Ivan Kochurkin ***@***.***> wrote:
The entire antlr4 is actually out-of-date, no big improvements are planned.
—
Reply to this email directly, view it on GitHub
<#4552 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7TMBRPOSU7QOOGBYSYBTYXQW4XAVCNFSM6AAAAABEOV4Q6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBXGE3TCNZWGA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
To clarify, "go get" is a complicated thing and does not cope well with the module being buried down in the main repo. Hence there is a release repo at antlr-go and this is the one that should be used. There are some trivial changes in the main repo that I have not coped over, but they were specific things for Google that you will not need. Other than those changes, the Go runtime is up to date.
…On Mar 10 2024, at 8:10 am, Jim Idle ***@***.***> wrote:
Basically there are two changes in the dev repo that I need to bring over to the release repo and then re-tag.
You should use ANTLR-go repo.
On Sun, Mar 10, 2024 at 04:13 Ivan Kochurkin ***@***.*** ***@***.***)> wrote:
>
>
> The entire antlr4 is actually out-of-date, no big improvements are planned.
> —
> Reply to this email directly, view it on GitHub (#4552 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAJ7TMBRPOSU7QOOGBYSYBTYXQW4XAVCNFSM6AAAAABEOV4Q6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBXGE3TCNZWGA).
> You are receiving this because you are subscribed to this thread.
>
|
@parrt - this can be closed :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hi, i'm a bit confused about where i should be importing to get the latest code.
when i followed the subdirectory here, my go client constantly is letting me know that you say I should use antlr4-go
7d39301
but when i look at antlr4-go, i see that commits don't happen in the new repo, they happen here.
i would prefer that the place where the go client doesn't warn me about would have the latest code,
maybe there is a ci-process that isn't running?
thank you
The text was updated successfully, but these errors were encountered: