-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(examples): prefer Go and Gno for respective language names #1607
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1607 +/- ##
==========================================
+ Coverage 55.79% 56.57% +0.78%
==========================================
Files 436 438 +2
Lines 66168 67094 +926
==========================================
+ Hits 36917 37961 +1044
+ Misses 26360 26186 -174
- Partials 2891 2947 +56
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Makes sense to me. |
Does this mean we need to change previous content to reflect this? There are many places where it's written Gnolang (Gno) and we usually have that in the context of... "Gnolang (Gno) is an interpreted and deterministic version of Golang (Go)." |
@ccomben ideally, yes, but I would say to prioritise places which are "timeless" (ie. website and docs) and to work on a best-effort basis for "historical" stuff (ie. blog, old tweets). Of course of the latter the blog is the most important (thank you for creating the issue!). |
More on my crusade for right terminology and avoid dooming us to have "gnolang" as the official language name.
See-also #1548