-
-
Notifications
You must be signed in to change notification settings - Fork 422
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
Incorporate support for raw string literals #485
Conversation
Hello @antonmedv, I kindly request your review of this pull request when you have a moment. Your insights would be greatly appreciated. Thank you in advance for your time and assistance! |
Nice! But I'm thinking about adding byte strings later as well.
So maybe it is better to add raw strings was a prefix?
But allow back quotas to be multi line?
|
I recommend that we reserve the |
If you aim to implement raw strings with the |
What is reason? |
Backticks are inherently interpreted as raw strings, which means there's no need to use escape sequences. However, when using quotes to implement raw strings, escape sequences become essential. |
That's why I believe there is no need for the |
I see. This makes good point. I was thinking about how raw string implemented in python. |
While Python uses the r prefix for raw strings, Go achieves this using backtick symbols. // Go Using backticks for raw string
rawString := `This is a raw string in Go.
It can span multiple lines and include "quotes" without escaping them.` # python Using the 'r' prefix for raw string
raw_string = r"This is a raw string in Python.\nIt can include escape characters like \n, \t, etc., without any special effect." We can achieve raw strings in two ways: using the r prefix or with backticks |
Ok. Let me review pr more carefully. |
The current parser lacks support for raw string literals