-
Notifications
You must be signed in to change notification settings - Fork 51
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
Adding str
support back
#369
Conversation
Type::Slice(hir::Slice::Str(_, hir::StringEncoding::UnvalidatedUtf8)) => { | ||
Type::Slice(hir::Slice::Str( | ||
_, | ||
hir::StringEncoding::UnvalidatedUtf8 | hir::StringEncoding::Utf8, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: we should emit docs, yes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or are we relying on cpp2's lack of docs? if so we should have an issue filed for that and note that str validity should be added
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was assuming we'll continue using the current cpp docs for cpp2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, cpp2 has a different structure.
Diplomat will generate C++ docs that say invalid UTF-8 is UB. However, this is not inline documentation, so I'm not super happy with this.
#57