Skip to content
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

Make it easier to parse rules_go's .bzl files with Go Starlark #4140

Merged

Conversation

EdSchouten
Copy link
Contributor

What type of PR is this?

Feature

What does this PR do? Why is it needed?

I'm doing some experiments, where I'm trying to parse rules_go's source code with Go Starlark so that I can analyze it. In the process I've noticed that there are some small constructs that Go Starlark doesn't seem to like. In both those cases It looks like Go Starlark works as intended.

Which issues(s) does this PR fix?

n/a

Other notes for review

Even though Bazel itself permits it, the Go Starlark interpreter does
not. I think the Go Starlark interpreter is correct here, because plain
Python also doesn't permit it.
@EdSchouten
Copy link
Contributor Author

Dear lord. Bazel itself doesn't support \u, even though it was added to Starlark three years ago:

bazelbuild/starlark@7f53743

Let me remove the commit that was converting \x to \u for now.

@EdSchouten EdSchouten force-pushed the eschouten/starlark-conformance branch from ca51b01 to 7d3b73d Compare October 9, 2024 12:08
@fmeum fmeum merged commit 9c8c142 into bazel-contrib:master Oct 9, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants