-
-
Notifications
You must be signed in to change notification settings - Fork 188
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
Cheatsheet: Gleam for Go users #413
Comments
So I voted for Go the other day on Twitter, and here I see there is an issue already :) Would you mind if I try to write that cheatsheet? I know Go but not Gleam yet. I'm open to learn something. |
That would be really cool! Go for it! Also don't feel it needs to be finished or perfect before you share it. A work in progress is still very useful, and others can help out too then |
Cool. Forked and working on it. |
Awesome @marcellanz |
Still working on it :) – times limited at the moment but I'm excited to have a great cheatsheet. |
Wonderful, thank you! |
Still working on it. Sorry for the delay. |
Good to hear, looking forward to it. Thank you. |
hey @marcellanz it's been a little while since this ticket was updated, has there been any progress? I don't mind taking it off your hands if you don't have time to work on it |
@TanklesXL please do. Thanks :) |
@marcellanz do you have a link to existing work you'd like me to build off of or would you rather i start from scratch? |
@TanklesXL please start from scratch – if you like I could review. |
@TanklesXL If you don't plan on working on this, I am happy to take the baton. I've been doing Go pretty intensively the past year and have been in touch with Gleam since very early and am currently reimplementing a type-safe templating engine I wrote in Go over to Gleam. So it will be easy for me to document things as I, uh, Go. 🙃 |
@gamebox in the end I never got a chance to pick this up so if you want to grab it feel free to take a crack at it. |
In the style of https://gleam.run/cheatsheets/gleam-for-elixir-users/
The text was updated successfully, but these errors were encountered: