Skip to content
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

Revert "Translator: allow go, but not by default" - Go translator is no worse than others #119

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

Mingun
Copy link
Contributor

@Mingun Mingun commented Apr 11, 2024

The Go translator is not included into all category since 0590480, which is strange. It's implementation not worse that, for example, Construct translator and it actually have more high rating on https://ci.kaitai.io.

Copy link
Member

@generalmimon generalmimon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I've been a little annoyed for a while now that I had to type -t all -t go every time, but not enough to do anything about it.

@GreyCat mentioned that Go is not included in -t all because the KST translator used to crash due to "NotImplemented errors", see #75 (comment).

However, if I try ./spec_kst_to_all -t all --all-specs -f now (with this PR's changes), it reaches all specs up to the last zlib_with_header_78 without problems, even though there are 21 scala.NotImplementedErrors when generating .go specs (20 times due to unimplemented doCast, once due to unimplemented testException). So I agree there is no reason to discriminate against Go anymore.

@generalmimon generalmimon merged commit efc21a0 into kaitai-io:master Jul 8, 2024
@Mingun Mingun deleted the stop-go-humiliation branch July 9, 2024 04:16
@Mingun
Copy link
Contributor Author

Mingun commented Jul 9, 2024

testException is implemented in #123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants