Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Up until this point most errors result in a panic. This is useful when early stages debugging but it would be extremely painful for anyone trying to properly use the tool if every tiny infringements caused the whole process to stop.
This PR will print errors and warnings as comments at the top of the file, but try to continue sensibly so that it will produce the best Go it can even if that turns out to be not completely correct.
I am testing this on the whole amalgamated SQLite3 source code. Obviously c2go is not at all mature enough to transpire this. However, if i can get it to spit out lots of warnings and at least produce some Go it will be a major step in the right direction.
I have a feeling this PR will turn out to have a great lot of changes so it's likely it will have around for a while, then get it's own release.
This change is