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
I don't have a strong preference either way, but I think it would be nice if Runic normalized to one or the other. The only potential issue is that it's technically possible to redefine nothing inside a module or function, but I have yet to see any code in the wild which does this.
The text was updated successfully, but these errors were encountered:
I would argue that even in the case of 2., the function still returns a value of nothing, irregardless whether it's used or not, so I would say making that explicit via return nothing is not necessarily bad
FWIW, I'd also vote for normalising to return nothing. In addition to @simeonschaub's point above, to me, the (subtle) communicative aspect of distinguishing between return and return nothing is outweighed by the advantage of clarity and consistency.
I don't have a strong preference either way, but I think it would be nice if Runic normalized to one or the other. The only potential issue is that it's technically possible to redefine
nothing
inside a module or function, but I have yet to see any code in the wild which does this.The text was updated successfully, but these errors were encountered: