-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/compile, go/types2: for case sensitive mismatches in function/method/attribute lookups please suggest "but does have $<CASE_INSENSITIVE_EQUIVALENT>" #70549
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
Comments
Change https://go.dev/cl/631356 mentions this issue: |
CC: @golang/compiler |
Thanks. This is a plausible usability improvement for the compiler. If we open this door, it would be nice to try to identify a good enough and helpful subset once. It seems like a lot of details need to be ironed out.
cc @griesemer |
Note that we already do matches if the case of the first letter differs.
|
Change https://go.dev/cl/662775 mentions this issue: |
Thanks @odeke-em for this issue and your CL. After reviewing your CL and also thinking about @timothy-king 's questions, we decided to borrow from @odeke-em 's code (thank you!) but go with a slightly simpler approach. We can always refine as needed. cc: @mrkfrmn |
Anytime @griesemer, gladly and thank you for picking it up! |
Go version
go version devel go1.24-2b33434287 Fri Nov 8 01:06:04 2024 +0000 linux/amd64
Output of
go env
in your module/workspace:What did you do?
While working on some terse library with a ton of symbols/functions, in which the nomenclature for a bunch of symbols at times defies expectations in case, I had such code
to reference https://pkg.go.dev/google.golang.org/grpc#WithChainStreamInterceptor and https://pkg.go.dev/google.golang.org/grpc#WithChainUnaryInterceptor
What did you see happen?
What did you expect to see?
If there is a case insensitve mismatch, kindly please suggest the first one so that the user can trivially fix their code instead of
having to eye-ball to figure out their typo.
The text was updated successfully, but these errors were encountered: