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
{.procvar.}
still used despite being the default and not documented
#12975
Comments
|
{.procvar.}
not documented{.procvar.}
still used but was documented
{.procvar.}
still used but was documented{.procvar.}
still used despite being the default and not documented
|
Then it should be removed, and not documented, but I see you edited your issue to reflect that :) |
I stumbled across this same issue today:
All I wanted to do was attempt to send a PR for unicode.nim, but then I saw the /cc @Araq |
This pragma did nothing. Ref: - nim-lang#2172 (comment) - nim-lang#12975
#14359 fixes this partially. |
This pragma did nothing. Ref: - #2172 (comment) - #12975
@Araq Thanks for merging that PR. Now grepping for
I am not sure how to remove or modify procvar references in those. Apart those those, grepping just |
well looks like procvar distinction still matters after all; I just retried #2172 (comment) and still relevant: proc `+`*(x: int): int {.magic: "UnaryPlusI", noSideEffect.} proc foo[T](a: T,
b: T,
f: proc(x: T, y: T): T): T =
return f(a,b)
let a = 11
let b = 10
let z = foo(a,b,`+`)
echo z
|
Not related to procvar though, but to the fact that |
This pragma did nothing. Ref: - nim-lang#2172 (comment) - nim-lang#12975
refs nim-lang#12975. doesn't close it because wProcvar isn't removed
refs #12975. doesn't close it because wProcvar isn't removed
This pragma did nothing. Ref: - nim-lang/Nim#2172 (comment) - nim-lang/Nim#12975
refs nim-lang#12975. doesn't close it because wProcvar isn't removed
{.procvar.}
is still being used but is not documented:The only doc is from ast.nim (but it doesn't end up in docs):
sfProcvar, # proc can be passed to a proc var
and yet, apparently procvar is now on by default according to #2172 (comment)
proposal
The text was updated successfully, but these errors were encountered: