-
Notifications
You must be signed in to change notification settings - Fork 37
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
Error message around <bytes>.decode(...) mention hilti::Charset #1803
Labels
Comments
Both of these are a result of the layering, where things get lowered from Spicy to HILTI internally, and doing "HILTI stuff" ends up working as well, and error messages may be produced at the HILTI level (where |
rsmmr
added a commit
that referenced
this issue
Oct 18, 2024
We now show them with a `spicy` prefix, which makes more sense for users. Closes #1803.
rsmmr
added a commit
that referenced
this issue
Oct 18, 2024
We now show them with a `spicy` prefix, which makes more sense for users. Closes #1803.
rsmmr
added a commit
that referenced
this issue
Oct 21, 2024
We now show them with a `spicy` prefix, which makes more sense for users. Closes #1803.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I thought there were some changes that hilti::Charset isn't supposed to be used anymore. Two observations:
bytes.decode("utf-8")
shows a lot ofhilti::Charset
for me:import hilti
works still?Am I confused? :-)
The text was updated successfully, but these errors were encountered: