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

Fix column number of map's opening bracket #13601

Conversation

peaceful-james
Copy link
Contributor

@peaceful-james peaceful-james commented May 25, 2024

To help finish
rrrene/credo#1136

To fix rrrene/credo#1132

@lukaszsamson
Copy link
Contributor

Won’t this break map meta in AST? It was recently fixed in fd4e6b5. Before 1.17 meta column was off by one.

@peaceful-james
Copy link
Contributor Author

peaceful-james commented May 25, 2024

Won’t this break map meta in AST? It was recently fixed in fd4e6b5. Before 1.17 meta column was off by one.

Yes, the PR you reference introduced this bug.

It seems kind of obviously wrong when you read it.

If %{ is at column X
then { is at column X + 1

But I am quite ignorant about all of this. I especially lack awareness of the larger context.

@josevalim
Copy link
Member

The tokenizer is 100% private API. We don’t guarantee compatibility on its output and no project should invoke it. The column positions are used internally for our needs. Thank you.

@josevalim josevalim closed this May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Elixir 1.17 issues
3 participants