hey folks! I was wondering if help was needed with updating any docs/guides/examples to the new syntax?
is the syntax stable enough for that? were you planning on doing this automatically somehow using AI stuff?
I'm available to help out with stuff that don't need Zig expertise :)
I have a project for this effort: https://github.com/rickhull/roc-init I am fairly new to Roc, and this project is very much an LLM-driven effort. Please poke around, and PRs are welcome, and direct repo access is on the table as well.
It's maybe too early to for roc-lang to start committing to maintaining official docs for new-roc, implying a level of support and stability that may not exist, so this project is a little bit of a pit stop where things can be worked on, verified, vouched and confirmed, before graduating to official docs, at the right time, if ever. It is meant to inform the approach to official docs, when the time is right
Some discussion here: #show and tell > roc-init repo (should we move any further discussion out of the show and tell channel?)
oh! got it!
I was following @Luke Boswell 's messages on those new compiler updates. IIRC it says the work on docs/guides did not yet start... So if roc-init is the "currently/temporarily official" playground for this stuff, maybe it could be mentioned there? :blush:
@Georges Boris good to see you again :wave:
I don't think we are ready right now to update the docs/guides/examples to the new syntax. I've been itching to jump into this myself but we are currently ironing out some bugs before we continue the basic-cli migration.
I mentioned in my announcement more as an FYI that these things don't exist yet, so working in the new Roc space is a difficult thing right now if you aren't super involved in all the PR's rolling through and the zig compiler.
I think as a milestone we should complete basic-cli and then we can really unlock working all these other things like exercism or examples.
I've held off working on bsic-cli the last few weeks and prioritized show stopping bugs or features like the dev backends.
The syntax is definitely very stable... but without the platforms being upgraded and docs landed it's pretty challenging.
We are very close though... it's hard to predict. I would say we are dealing with the most complexity right now and so the uncertainty is also at a maximum point.
When we have all the backends (dev, wasm, llvm, interpreter) passing all the tests and evaluating the same answers, without any ref-counting leaks... we will have effectively resolved all the complexity and from there on it's just a matter of wiring the remaining things together and polishing.
got it! I completely understand this messy moment that is just too much effort to explain people on the outside... the most sane thing is just to go past it, remove complexity and then onboard people.
if there is anything you think could use the extra hands without burdening you folks - let me know! otherwise I'm happy to wait until the right time :)
if there is anything you think could use the extra hands without burdening you folks - let me know! otherwise I'm happy to wait until the right time :)
If you saw the discussion in the other channel, I have a TODO to take Anton's verification of SUSPICIOUS_REFERENCES and to fix those by hand. I will probably get to that in a week. You could take a look if interested, and I can answer any questions.
Last updated: Feb 20 2026 at 12:27 UTC