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 believe that demonstrating "code best practices" is a general ideal for the tutorial. With the caveat of "unless it blurs the point".
I think in the case of the example code in ponytest section that adding \nodoc\ to the test code as we have throughout the standard library and various ponylang libraries makes sense in that, it shouldn't obscure the meaning of the code and helps enforce the existence of the annotation.
The one drawback to this right now is that non of the syntax highlighters we use understand annotations and as such, syntax highlighting will be broken.
The text was updated successfully, but these errors were encountered:
My preference as expressed in the sync call, is that I think we should fix the syntax highlighter that renders the tutorial before updating the tutorial
I believe that demonstrating "code best practices" is a general ideal for the tutorial. With the caveat of "unless it blurs the point".
I think in the case of the example code in ponytest section that adding
\nodoc\
to the test code as we have throughout the standard library and various ponylang libraries makes sense in that, it shouldn't obscure the meaning of the code and helps enforce the existence of the annotation.The one drawback to this right now is that non of the syntax highlighters we use understand annotations and as such, syntax highlighting will be broken.
The text was updated successfully, but these errors were encountered: