James Clark comments

Results 508 comments of


                                            James Clark

Should local unused variables be a compile-time error?

If anybody has comments on how this issue should be decided, please add them here.

Should local unused variables be a compile-time error?

Note the example in #352: this undermines the compiler's checking for not ignoring error returns.

Should local unused variables be a compile-time error?

Do this as a linter thing in a Swan Lake update.

Should local unused variables be a compile-time error?

Is there any reason warnings should not be given in your bulleted cases? If you're looping and you don't want to use the loop variable, you can do `foreach var...

Should local unused variables be a compile-time error?

I think it would be good for the spec to say that it is planned to make this an error in the future.

Should local unused variables be a compile-time error?

> One option is that we don't generate this warning when a range expression is used in a `foreach` statement. I think this is a good solution. From the user's...

Should local unused variables be a compile-time error?

@MaryamZi Yes.

Should local unused variables be a compile-time error?

We should make this a warning in 2022R1 spec.

Write proper spec for @typeParam annotation

Also see #453. @hasithaa notes that we may have a similar problem when using a @typeParam with arguments of function type, since function arguments are contravariant.

Write proper spec for @typeParam annotation

New functionality needed is #457.