Delay "Tuples are not allowed" until emit time #282
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.
Typeshare can't handle Rust types which contain a tuple. This is annoying, because my Rust types do contain a tuple! But it's even more annoying because I'm planning to tell typeshare explicitly what those types should become in the target language using the
type=decorator - so it doesn't even matter that my types contain tuples, because they're immediately overridden and Typeshare doesn't even need to care about them.This PR moves the parse-time failure to emit time, by storing the parse failure inside a
RustType::Unrepresentablevariant. If thisRustTypehas a type override, then there's no problem; if there are no type overrides, the unrepresentable type can't be emitted, and then there's a problem.So: