You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After #3534, now we have 3 different ways to access the calculated variables:
after_stat(var)
stat(var)
..var..
Though it seems very difficult to remove other syntax than after_stat(), I think we should promote the most proper one a bit more eagerly to avoid confusion. Can we warn on the usage of stat() and ..var..-notation?
The text was updated successfully, but these errors were encountered:
yutannihilation
changed the title
Deprecate on stat() and ..var..-notation?
Warn on stat() and ..var..-notation?
Jan 7, 2020
I think we should (promote it more aggressively), but I also think instantly deprecating the other flavours upon release is a bit too agressive. It will be mentioned in the release post, and all docs have been updated to use it (and stat() has been removed from the doc)
I think we should begin warning sometime after this release
Thanks, fair enough. But, I'm a bit pessimistic about the impact of docs as I see many people even don't know the existence of stat() after 1.5 years passed since the release (version 3.0.0)...
Anyway, I agree with you it's not the time to add warnings in the upcoming release. Let's wait for a while.
After #3534, now we have 3 different ways to access the calculated variables:
after_stat(var)
stat(var)
..var..
Though it seems very difficult to remove other syntax than
after_stat()
, I think we should promote the most proper one a bit more eagerly to avoid confusion. Can we warn on the usage ofstat()
and..var..
-notation?The text was updated successfully, but these errors were encountered: