Aurélien Geron (Oct 13 2026 at 00:01): Aurélien Geron (Oct 13 2026 at 00:01):Now that the language seems pretty stable, it might be time to organize a docathon to update all the docs? Perhaps a few volunteers can prepare a list of docs to update/write and provide some general instructions, then anyone can contribute over a weekend or a week?
Luke Boswell (Oct 13 2026 at 00:17):Is the langref link to the website broken? the langref is complete, but the website says it is heavily WIP and there is a lot missing i.e
Luke Boswell (Oct 13 2026 at 00:18):Other than the Tutorial which Richard has said he wants to write ... what other docs need updating?
Aurélien Geron (Oct 13 2026 at 04:31):Yeah, it's this sentence "This is heavily WIP!" that made me think we need to complete/update the docs before 0.1.0. If the langref is already done, great! :grinning_face_with_smiling_eyes:
I ran into a number of outdated statements here and there, such as saying that an if must always have an else, even though this is no longer true since we have return now.
The playground is also outdated, I'm not sure why (I thought we had fixed that).
The examples page feels disorganized. It should perhaps be organized by categories, and/or examples should perhaps have tags about their main concepts or main API.
Things feel a bit disjointed: perhaps the langref and standard lib docs should point to examples, and vice versa.
Also, several things are not covered by examples, if I'm not mistaken:
for, while, and var versus foldwhere constraintsMoreover, having some examples of common packages and platforms would be good, such as unicode (in more depth), path, roc-ray, etc. Alternatively we could just point to these packages, but right now we have examples for basic-cli, basic-webserver, http, roc-ascii, roc-parser, and roc-random, so I think it would make sense. The platform and package examples should each be in their own section in the examples page.
Perhaps a "Tips and tricks" or "Best practices" page would be useful, and a docathon would help figure out what to recommend. For example I like to use Try(Foo, _) during dev and be more specific only at the end, switching to Try(Foo, [A, B, C]).
There's certainly more to do. Completing this To-Do list is what I suggested for step 1. Perhaps there's not enough work to justify step 2, but in many projects I've worked on, the docs weren't get enough love, and I've found that a short focused effort is a good solution to solve that.
Luke Boswell (Oct 13 2026 at 04:45):Richard Feldman said:
The focus from there would be fixing bugs without regressing other things, which I'd like to do by getting a corpus of projects that work on RC1, and having CI tell us when we have broken them in a nightly release.
The broader examples might tie in nicely with the new requirement we have for testing things outside the repository -- the failing examples would tell us when we have broken things downstream, but also not block PRs.
Luke Boswell (Oct 13 2026 at 04:48):I've been setting up my CI workflows so I can know when a nightly breaks something (either I need to patch the platform and make a new release, or report a bug back upstream).
Aurélien Geron (Oct 13 2026 at 04:50):I'm happy to submit a few new examples. Btw, several examples are in the examples repo but not online (e.g., custom literals, hello web, webapps with Elm, sorting strings, multiline-comments)
Luke Boswell (Oct 13 2026 at 04:57):The website and CI supporting that definitely need some love :smile:
Aurélien Geron (Oct 13 2026 at 05:05):The benefits of a docathon go beyond simply improving the docs: it can be a fun community-building activity, an opportunity to discover & discuss other issues, and a way to get people to care more about docs if they've contributed to them.
Aurélien Geron (Oct 13 2026 at 05:21):Apparently the reason why the website is still using an old playground and is missing several examples is that the latest Cloudflare production build failed. I'm not sure who has the Cloudflare logins, but they are needed to access the Cloudflare logs to determine what the problem is.
ChatGPT suggests that a likely build blocker is builtin documentation generation: main still uses the old command, while PR #157 switches to the required roc docs --builtins.
Anton (Oct 13 2026 at 12:38):I am looking at the cloudflare build failure, the website is out of date because of the large amount of breaking Roc changes, things that break after updating and other random issues.
Anton (Oct 13 2026 at 12:41):it might be time to organize a docathon to update all the docs?
Richard mentioned (I'm paraphrasing) in the last meetup that he's opinionated about the docs, so we want to make sure that we're not just filling out the docs in a distributed effort.
Anton (Oct 13 2026 at 14:34):The website has been successfully updated :tada:
Aurélien Geron (Oct 13 2026 at 17:59):Sounds good, thanks @Anton.
TeaDrinkingProgrammer (Oct 14 2026 at 06:57):As I mentioned previously, I would like to contribute too, but I don't write Roc (yet) so feel free to tag me as a reviewer. Might even be helpful to have a perspective from someone who is not in the weeds as much. I'll also see id I can push my previous feedback as PRs
Aurélien Geron (Oct 15 2026 at 10:15):I've submitted PR #163 to organize the Examples page into sections and give each example a little description:
Aurélien Geron (Oct 15 2026 at 10:24):I also submitted PR #310 with 26 new examples covering more Roc language features, packages, and platforms:
Types and functions
Box.where constraints and reusable aliases.map and map!.Collections and iteration
for, while, var, and fold.for!, and custom file-reading streams.Error handling
? inside expect.Parsing and encoding
Organizing and publishing code
roc docs.Packages
Platforms
Aurélien Geron (Oct 15 2026 at 10:40):I put them all in one PR for convenience, but if you want me to break it into smaller chunks, please let me know.
Anton (Oct 18 2026 at 17:28):Aurélien Geron said:
I put them all in one PR for convenience, but if you want me to break it into smaller chunks, please let me know.
Yes please :sweat_smile: I'd love to be able to get quick reviews done between other things.
Thanks for making all of them :heart:
Aurélien Geron (Oct 19 2026 at 02:08):No problem @Anton , I just submitted 26 PRs (#316 to #341), and closed the big one (#310). It's more digestible now. :sweat_smile:
TeaDrinkingProgrammer (Oct 25 2026 at 09:30):Anybody has time to look at this one or is the mini-tutorial going to be replaced? https://github.com/roc-lang/roc/pull/11729
Anton (Oct 25 2026 at 18:17):Yes, we indeed plan to replace it before 0.1
Aurélien Geron (Oct 27 2026 at 22:25):There are 15 new code examples on the website, check them out!
Thanks to @Anton who reviewed them all, and to @Luke Boswell for reviewing the PR to update the website.
Luke Boswell (Oct 27 2026 at 22:25):Love your work polishing all these examples and sharing that with the community. I am sure many people will find this helpful to follow Roc 0.1 and all the changes in our new compiler.
Hardy (Oct 28 2026 at 21:50):Currently browsing through those examples. Very nice so far.
Found a minor bug: the link on the https://www.roc-lang.org/examples/RecursiveTypes/README page towards the nested types example is broken (i.e. there is an ".md" at the url end) and also the other direction the link on the nested to the recursive types page.
Aurélien Geron (Oct 28 2026 at 22:00):Thanks Hardy, I'll fix these.
Luke Boswell (Oct 28 2026 at 22:02):I was just looking at our syntax highlighting on the website... I feel like we could replace it with the tree-sitter wasm module and that would give us more fidelity and better highlighting. I'm not sure about the trade-off and haven't looked into it. Or perhaps we could use roc-parser now that has Roc syntax. Just leaving the thought here, I might look at this and explore the options later.
Richard Feldman (Oct 28 2026 at 23:23):I'd rather not do that
Richard Feldman (Oct 28 2026 at 23:24):I already ported our real tokenizer to JS and simplified the code to get it to a small asset size
Richard Feldman (Oct 28 2026 at 23:24):I think if we switched to tree-sitter we would end up with a bigger asset, that ran slower (bc wasm is async so there would be a flash of unstyled content) and with actually less fidelity than what we have now :smile:
Luke Boswell (Oct 28 2026 at 23:24):Alg, I just though the current highlighting could be better (as compared to tree-sitter etc) but I didn't look into it.
Luke Boswell (Oct 28 2026 at 23:25):We could just improve the JS I guess, it's probably not hard
Luke Boswell (Oct 28 2026 at 23:26):Do you remember which repository has all that?
Luke Boswell (Oct 28 2026 at 23:27):found it
Luke Boswell (Oct 28 2026 at 23:38):I forgot I already did a heap of work on our zig compiler semantic tokens -- so I can just re-use that in a differential harness to help improve the JS.
Luke Boswell (Oct 28 2026 at 23:38):That uses type checked CIR as the authority.
Richard Feldman (Oct 28 2026 at 23:45):cool, sounds good!
Luke Boswell (Oct 29 2026 at 00:15):Didn't take long at all.. this is the home page after the first pass
Aurélien Geron (Oct 29 2026 at 00:16):Very nice! The dark purple might be a little bit hard to read.
Richard Feldman (Oct 29 2026 at 00:25):yeah I'm also not a fan of the yellow, if we can avoid it
Richard Feldman (Oct 29 2026 at 00:26):I feel like purple, teal, gray, and black/white (depending on light mode vs dark mode) are uncontroversial since those are part of the color scheme, and if we really need another one, I'd go with some shade of blue that looks nice with the purple and teal
Luke Boswell (Oct 29 2026 at 00:27):I'll iterate on it a little after lunch. I'm also adding a script that checks WCAG AA for our colors, I think we already did that and I'm not proposing we change them.
Luke Boswell (Oct 29 2026 at 00:28):Also do we have plans to lift the tutorial back into the website from a markdown document? Even if it's just in its current form?
Aurélien Geron (Oct 29 2026 at 01:05):FYI, I'm planning to work on these improvements to the docs in the next few days:
If you have any suggestions, please let me know!
Aurélien Geron (Oct 29 2026 at 01:40):PR #179 moves the tutorial to the website.
Luke Boswell (Oct 29 2026 at 01:50):I was thinking about giving the Install pages some love... but I'm not sure
Aurélien Geron (Oct 29 2026 at 01:58):Yes, it probably needs just a little bit of text, but I like how straight-to-the-point it currently is, so we don't want a wall of text either. The "Build Roc from Source" page could also be lifted into the website.
Luke Boswell (Oct 29 2026 at 02:24):I dont mind this pallet
Aurélien Geron (Oct 29 2026 at 02:27):Beautiful! The dark purple is still a bit too dark for me, but I could live with it.
Aurélien Geron (Oct 29 2026 at 02:44):
The right curly bracket should be purple too.
Luke Boswell (Oct 29 2026 at 02:45):haha already got that one :sweat_smile:
Luke Boswell (Oct 29 2026 at 02:46):I've found a bunch of others too, doing another round of cleanup
Luke Boswell (Oct 29 2026 at 03:09):I've been doing some research to find good categories for "semantic roles"
Aurélien Geron (Oct 29 2026 at 03:19):I've done these points:
It looks like this:
Any suggestions before I submit the PR?
Luke Boswell (Oct 29 2026 at 03:22):Looking good. I'd nitpick some alignment things, like the search bar
Aurélien Geron (Oct 29 2026 at 03:24):Ah good point. I wanted to avoid using vertical space (especially for mobile devices), but the search bar will just scroll to the top when the user scrolls down, so that's not a problem. I'll lower it to the level of the "Docs Home" text in the panel.
Luke Boswell (Oct 29 2026 at 03:29):Screencast from 2026-10-29 14-28-18.webm
Aurélien Geron (Oct 29 2026 at 03:32):Very nice.
There are a few colored letters here and there (you probably noticed already):
Luke Boswell (Oct 29 2026 at 03:32):I think thats just the recording being goofy
Luke Boswell (Oct 29 2026 at 03:44):Here's the site preview from the PR https://semantic-highlighting-roc.cc02oj5kr.workers.dev/
Aurélien Geron (Oct 29 2026 at 04:39):Just submitted PR #181 to add some content to the Docs landing page and keep the same header as the rest of the site. I believe I fixed the alignment issues; it now looks like this:
And on a phone:
pixelsprout (Oct 29 2026 at 04:54):Aurélien Geron said:
Just submitted PR #181 to add some content to the Docs landing page and keep the same header as the rest of the site. I believe I fixed the alignment issues; it now looks like this:
And on a phone:
The search and hamburger don't quite line up with the content gutters. Minior nitpick though :wink:
Aurélien Geron (Oct 29 2026 at 04:58):Oh good point, thanks, I only checked the alignment on the Desktop.
Fixed:
Steve Howell (Oct 29 2026 at 12:09):#contributing > markdown may be relevant here.
Jonathan (Oct 29 2026 at 12:19):Aurélien Geron said:
Just submitted PR #181 to add some content to the Docs landing page and keep the same header as the rest of the site. I believe I fixed the alignment issues; it now looks like this:
And on a phone:
I feel like this is a very minor nitpick, and it's miles better than what came before, but I haven't seen much other use of rounded corners in the rest of the roc site, and imo it jars a bit here. E.g. navigation borders, search box, Examples/FAQ section underlines, code snippets in docs. I'm not the biggest sharp-corners fan, but I did feel like it was a bit of the website's charm.
Jonathan (Oct 29 2026 at 12:19):(Thank you for working on this!!!)
Anton (Oct 29 2026 at 14:36):Yes, no rounded corners please, I think I once made a CI check for that. The logo is very sharp and geometric, so rounded corners don't really fit with that. Thanks for working on this though :heart:
Aurélien Geron (Oct 29 2026 at 18:54):Sounds good, I'll tweak that. :+1:
Aurélien Geron (Oct 29 2026 at 19:50):Here's the new look without rounded corners:
Anton (Oct 29 2026 at 20:01):I like it :)
Anton (Oct 29 2026 at 20:09):One minor thing I would change is "join the community". It asks for immediate commitment, the reader may not feel ready to join the community and have doubts about what that will set in motion. "Take a look at our group chat" is low commitment and super clear about what the link will do. In most places mentioning the group chat we also add "we're friendly!", because that's not always the case for online communities.
Aurélien Geron (Oct 29 2026 at 20:19):Should "take a look at our group chat" point to the Community page or directly to Zulip?
Aurélien Geron (Oct 29 2026 at 21:00):Here's a quick demo of the new search experience I've been building:
I submitted two PRs:
Hope you like it!
Steve Howell (Oct 29 2026 at 21:02):Looks great!
notramo (Oct 29 2026 at 21:33):@Aurélien Geron, did you change the sorting somehow, or is this issue still relevant?
https://github.com/roc-lang/roc/issues/11522
Aurélien Geron (Oct 29 2026 at 21:37):There's a ranking algorithm now, but it doesn't put type names first, so let me fix that.
Aurélien Geron (Oct 29 2026 at 22:10):Fixed. :+1: I also prioritized matches at the beginning rather than the middle of a result, so Hasher comes before Crypto.BLAKE3.Hasher. Here's an example:
notramo (Oct 29 2026 at 22:17):Thanks.
notramo (Oct 29 2026 at 22:17):Is there some preview deployment where it can be tried out?
Aurélien Geron (Oct 29 2026 at 22:17):Not yet, I'll set one up.
Aurélien Geron (Oct 29 2026 at 22:18):Here's another example, showing that function matches come before signature matches:
Luke Boswell (Oct 29 2026 at 22:21):If you make a PR cloudflare will make a preview site
Luke Boswell (Oct 29 2026 at 22:22):This is looking really great. I love all the little details you've put in to make it feel super nice.
Aurélien Geron (Oct 29 2026 at 22:24):Great, I'll make a PR now. It combines three PRs: the Docs generator update, the search update on the website, and the website header update.
Aurélien Geron (Oct 29 2026 at 22:33):https://github.com/roc-lang/www.roc-lang.org/pull/184
Aurélien Geron (Oct 29 2026 at 22:33):@Luke Boswell will Cloudflare automatically generate a preview or do you need to authorize it?
Luke Boswell (Oct 29 2026 at 22:50):Trying to figure out why the bot triggered on my PR but not yours so far https://github.com/roc-lang/www.roc-lang.org/pull/180#issuecomment-6487202201
Luke Boswell (Oct 29 2026 at 22:51):I marked your's ready for review to see if that helps
Luke Boswell (Oct 29 2026 at 22:51):Ah it must be because your PR is from a fork
Aurélien Geron (Oct 29 2026 at 23:07):Here's the new Docs search preview
notramo (Oct 29 2026 at 23:07):
I think the double border around the category selector buttons is too dense. What about removing the rounded button borders and only adding a vertical separator from the top line to the ones below?
Something like this:
Aurélien Geron (Oct 29 2026 at 23:08):Good idea, I'll do that now
notramo (Oct 29 2026 at 23:09):I forgot the background highlight on the active button.
Aurélien Geron (Oct 29 2026 at 23:11):Yeah, I was thinking the same thing just now. I'll try out some things.
notramo (Oct 29 2026 at 23:12):Or maybe no vertical bars, just some small separator like a middle dot? ·
notramo (Oct 29 2026 at 23:13):Or keep the lower border and simply add a thicker bottom border, like this?
https://daisyui.com/components/tab/#tabs-border
notramo (Oct 29 2026 at 23:17):
The titles are not very distinct visually. Maybe a bold font would help?
notramo (Oct 29 2026 at 23:18):
The bottom border disappears when scrolling. I did not notice it when I recommended the above button border changes.
Aurélien Geron (Oct 29 2026 at 23:19):I'm trying center dots, no lines + underline selected + darker snippets (so the titles stand out more).
Aurélien Geron (Oct 29 2026 at 23:22):It looks like this:
notramo (Oct 29 2026 at 23:23):Seems better. The snippet button is a bit strange. Maybe no background?
notramo (Oct 29 2026 at 23:24):The "All" category seems good at first, but when I actually try to use it, it's not really useful. Most of the time, there are too many API results, so I would not scroll for the guides, but use the button.
What about removing it, and adding counters to the API and the guides buttons instead?
And maybe a quick button at the end of API results: That's all. Maybe try searching the Guides & examples (15) instead?
Aurélien Geron (Oct 29 2026 at 23:25):Oh you've got a good eye, I didn't even notice the background! :glasses:
I'll remove the background. I much prefer this look, thanks for the suggestions!
Btw, would you prefer a bit more margin between the results and the buttons?
notramo (Oct 29 2026 at 23:26):
The search cancel button is not well visible. Maybe use the same purple? Or add some background?
notramo (Oct 29 2026 at 23:26):Btw, would you prefer a bit more margin between the results and the buttons?
Yes, I would recommend that. Maybe if a fade or shadow effect could be added, that would help.
notramo (Oct 29 2026 at 23:27):I would recommend symmetric padding at the top of the buttons too.
Aurélien Geron (Oct 29 2026 at 23:44):Hows' this?
I'm not sure about removing the All button. I've used the search for a while, and what I liked is that pretty often what I'm looking for is right there, without extra clicks. For the API results, they're at the top, so no problem. But when I search for lang ref content, such as "Modules", "Platforms", or "Types", there are barely any API results so the thing I'm looking for is right there. And in the cases it's not (e.g., "JSON"), I just need to click on "Guides & examples", which I would have to do anyway if we removed "All".
notramo (Oct 29 2026 at 23:45):Seems good.
notramo (Oct 29 2026 at 23:46):What is the thick bar under the snippets button?
notramo (Oct 29 2026 at 23:46):Is it indicating that it's enabled/disabled?
Aurélien Geron (Oct 29 2026 at 23:46):Yes
Aurélien Geron (Oct 29 2026 at 23:46):It's off by default so the user will see the underline appear when clicking it
notramo (Oct 29 2026 at 23:46):What about using a toggle for it?
notramo (Oct 29 2026 at 23:46):https://daisyui.com/components/toggle/#toggle-switch
notramo (Oct 29 2026 at 23:47):By the way, is the docs vanilla CSS or is some UI framework used?
notramo (Oct 29 2026 at 23:47):Then I could link component examples from that (if any).
Aurélien Geron (Oct 29 2026 at 23:48):It's vanilla CSS and JS
Aurélien Geron (Oct 29 2026 at 23:49):I initially had a "Show snippet" button (which would be roughly as wide as a toggle + label), and it made the button bar too wide on mobile, they ended up on two lines
notramo (Oct 29 2026 at 23:49):Maybe a "Snippets" plus a toggle?
notramo (Oct 29 2026 at 23:51):It's confusing on mobile, because sometimes there's no visible effect when toggling it.
notramo (Oct 29 2026 at 23:53):And there's no label either.
notramo (Oct 29 2026 at 23:54):
Maybe utilize the full screen width on mobile? So there's no blank padding at the sides?
Aurélien Geron (Oct 29 2026 at 23:55):Sounds good, I'll give that a try.
notramo (Oct 29 2026 at 23:58):And maybe the border could be removed and use the full screen.
notramo (Oct 29 2026 at 23:59):Try it on a real mobile, not just the devtools mobile simulator.
notramo (Oct 29 2026 at 23:59):When the on-screen keyboard is open during search, it uses up half of the screen.
Aurélien Geron (Oct 30 2026 at 00:00):Trying all of this. I'm also adding snippets in the API section.
notramo (Oct 30 2026 at 00:03):My recommendation for mobile:
This would hide all other parts of the page. For example, the top menu unnecessarily takes up space during search.
Aurélien Geron (Oct 30 2026 at 00:15):It looks much better. I've also merged the two API sections into one, there's no good reason to separate them.
Next I'll work on the snippet toggle
Aurélien Geron (Oct 30 2026 at 00:23):Here's what it looks like now on mobile. I also added the toggle:
Aurélien Geron (Oct 30 2026 at 00:35):Here's the latest search preview.
Aurélien Geron (Oct 30 2026 at 00:38):Looks like this on my phone, with the on-screen keyboard:
Screenshot_20261030_133726_Chrome.jpg
Aurélien Geron (Oct 30 2026 at 00:40):And without the snippets:
Screenshot_20261030_134011_Chrome.jpg
notramo (Oct 30 2026 at 00:45):I like this version a lot more.
notramo (Oct 30 2026 at 00:47):
When focusing it on mobile, and it switches into full-screen mode, it's empty. I would recommend showing unfiltered results ("" query string), or some top picks.
Aurélien Geron (Oct 30 2026 at 01:40):Latest search preview with suggestions on mobile
Aurélien Geron (Oct 30 2026 at 01:43):It looks like this:
Luke Boswell (Oct 30 2026 at 01:43):this is just my opinion ... but it feels strange to have a super wide screen on my monitor, and then these code snippets are scrolling horizontally with so much empty whitespace
Luke Boswell (Oct 30 2026 at 01:44):I'm on a 1920x1080 monitor so nothing unusual
Aurélien Geron (Oct 30 2026 at 01:45):This is not related to my recent changes, I don't think. We could perhaps make it a bit wider indeed, but there comes a point where it looks like a wall of text and it's not as pleasant to read, imho.
Luke Boswell (Oct 30 2026 at 01:50):Its not related to the search
Luke Boswell (Oct 30 2026 at 01:51):I wonder if we could make a lint or something to warn if our code snippets were longer than 80 characters on a line or something
Luke Boswell (Oct 30 2026 at 01:51):That might be a bit crude but we could always break them over multiple lines I guess.
Aurélien Geron (Oct 30 2026 at 02:10):Yes, it would be nice if the doc for every function and type started with a short sentence that could be used as a snippet. :+1: Python imposes that, we could reuse the same rules. ChatGPT says:
Keep the first sentence under 72 characters: While general code lines can extend to 79 characters, PEP 8 specifically restricts flowing text blocks like docstrings and comments to a maximum of 72 characters.
Write as an imperative command: The summary should prescribe the function's effect as an action ("Do this", "Return that"). For example, use "Return the absolute value" rather than "Returns the absolute value".
End with a period: The summary line should always end with a period.
Isolate with a blank line: If you are writing a multi-line docstring, that first summary line must be separated from the rest of the deeper explanation by exactly one blank line.
Luke Boswell (Oct 30 2026 at 02:13):Is this how Python does it?
Aurélien Geron (Oct 30 2026 at 02:13):Yes, these are Python's rules
Luke Boswell (Oct 30 2026 at 02:15):I wonder if we will want to tailor the "imperative command" a little for Roc's functional approach. I'm really fuzzy on what that would look like, just "Return the absolute value" doesn't quite feel right
Anton (Oct 30 2026 at 06:31):By the way, on macOS responsively is great so you can see a wide variety of screen sizes and types at once.
Anton (Oct 30 2026 at 06:44):Aurélien Geron said:
Should "take a look at our group chat" point to the Community page or directly to Zulip?
Directly to zulip, the community page has too much text for the casually curious.
Aurélien Geron (Oct 30 2026 at 08:05):Oops, it looks like I forgot this change, the site still says "join our community", sorry. I just submitted PR #186 to fix that.
notramo (Oct 30 2026 at 10:52):Is it intentional that the /tutorial page does not mention the |> even once?
notramo (Oct 30 2026 at 10:52):Some LLMs think it's been removed in the rewrite or usage is discouraged.
Luke Boswell (Oct 30 2026 at 10:53):It was removed, and then it came back :sweat_smile:
Luke Boswell (Oct 30 2026 at 10:53):So not intentional, just not updated
Richard Feldman (Oct 30 2026 at 15:11):yeah the syntax for it changed to a different symbol in the initial rewrite, then later changed back
notramo (Oct 30 2026 at 18:30):Was the method syntax also added in the rewrite? Or did it exist in the old Rust version too?
Anton (Oct 30 2026 at 18:39):It was added in the rewrite
Aurélien Geron (Oct 31 2026 at 04:03):I'm now working on updating the langref. I submitted PR #12725 to fill gaps in the outline, give it more structure, clarify what exists todays vs what's planned, remove some obsolete limitations, soften the intro warning, and a few other things.
Here's the list of planned features mentioned in the langref. Now that we're approaching 0.1.0, it would be good to clarify which of these are planned for 0.1.0. @Richard Feldman?
..[])collection[key])continue Richard Feldman (Oct 31 2026 at 12:08):All of those will be after 0.1.0
Aurélien Geron (Oct 31 2026 at 20:38):Thanks, Richard. I think there are a couple of references to 0.1.0 in the langref, I'll be explicit about the fact that it will be after 0.1.0, to set expectations. Unless you want me to say "by 1.0.0"?
Richard Feldman (Oct 31 2026 at 22:01):let's just say after 0.1.0, no need to promise things unnecessarily :smile:
Aurélien Geron (Oct 31 2026 at 22:31):Thanks Richard. PR #12758 updates the langref to make this clear.
Aurélien Geron (Nov 01 2026 at 06:08):The new search is live, try it out!
Anton (Nov 01 2026 at 08:02):I like the "Try searching for..." suggestions :)
Last updated: Nov 04 2026 at 18:54 UTC