59 ms·
I find this very human-friendly: "[double colon] permits vectors to be defined inline without additional syntax such as [ ... ] or { ... }." (One could questio
by jampekka 1y ago
I find this very human-friendly: "[double colon] permits vectors to be defined inline without additional syntax such as [ ... ] or { ... }."
(One could question how human friendly it is to call lists and dicts "vectors" though...)
https://huml.io/specifications/v0-1-0/#why https://huml.io/specifications/v0-1-0/#why
- sippeangelo 1y agoIt's especially clear in the "inline dict" example. I really like it! props:: mime_type: "text/html", encoding: "gzip" # Inline dict.
- OJFord 1y agoBut that's not done for human readability, that's done for machine parsing? A human would understand just as well: props: mime_type: "text/html", encoding: "gzip" # Inline dict.
- F3nd0 1y agoFor me, it’s clearer with a double colon. Not intuitive, but extremely easy to get used to. When I see the first colon introduce a list, I have to go out of my way to not see the other colons as introducing lists.
- lucketone 1y agoMy mind has a feeling that this might be possible interpretation: props: [mime: [html, encoding:[gzip]]] (Even if not legal, to be sure, I must backtrack and concentrate on this particular piece) There are many different humans. I definitely like the idea to separate “:: vs :”.