Help explain purpose of !

[willnwhite]

No description provided.

[process-bot]

Thanks for the pull request! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

[process-bot]

Thanks for the pull request! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

[jvoigtlaender]

There is #678.

[jvoigtlaender]

There is #678.

[jvoigtlaender]

@willnwhite, any comment on the redundancy of your PR due to the older one I linked to?

[jvoigtlaender]

@willnwhite, any comment on the redundancy of your PR due to the older one I linked to?

[evancz]

@jvoigtlaender, curating issues and PRs is better done by maintainers, not folks who open stuff. I think the other one is too verbose, and I think this one may need some extra info. The right move is probably to just remove (!) entirely.

I don't know if you saw this talk I did recently, but one of the points I try to make is that it's fine to let stuff like this sit for a while. It looks like a PR, but it's really a report that (!) is kind of confusing.

[evancz]

@jvoigtlaender, curating issues and PRs is better done by maintainers, not folks who open stuff. I think the other one is too verbose, and I think this one may need some extra info. The right move is probably to just remove (!) entirely.

I don't know if you saw this talk I did recently, but one of the points I try to make is that it's fine to let stuff like this sit for a while. It looks like a PR, but it's really a report that (!) is kind of confusing.

[jvoigtlaender]

Particularly as a report rather than PR it seems a duplicate of that other one. But good to know how you want to handle this.

[jvoigtlaender]

Particularly as a report rather than PR it seems a duplicate of that other one. But good to know how you want to handle this.

[willnwhite]

I've read #678 and added some more info to this PR. I hope this could help newcomers, at least before any removal of (!) occurs.

[willnwhite]

I've read #678 and added some more info to this PR. I hope this could help newcomers, at least before any removal of (!) occurs.

[bukzor]

+1 to remove (!)

[bukzor]

+1 to remove (!)

[Pilatch]

Awesome. I was wondering what the heck this did.

[Pilatch]

@evancz I hear that ! is confusing, and that's a reason to remove it, but until it's removed, it would be a shame to not clear up that confusion for newcomers to the language.

[Pilatch]

@evancz I hear that ! is confusing, and that's a reason to remove it, but until it's removed, it would be a shame to not clear up that confusion for newcomers to the language.

[evancz]

The current plan is to drop this operator for the next release. If that does not happen, I will add it back with documentation.

[evancz]

The current plan is to drop this operator for the next release. If that does not happen, I will add it back with documentation.