rhombus-prototype icon indicating copy to clipboard operation
rhombus-prototype copied to clipboard

Brainstorming and draft proposals for Rhombus

Results 171 rhombus-prototype issues
Sort by recently updated
recently updated
newest added

Some initial Path integration that I've been poking at for a couple of weeks now. Initially, I used a veneer for `Path.read_with` and `Path.write_with` that were syntax and would take...

When I was reading the guide, I tried one of the examples described in it, but an error occurred. ## description When `fun zero()` and `statinfo.macro 'zero'` are declared at...

Example: ``` block: let g :~ Group = 'foo bar baz' let new_g :~ Group: let (prefix, content, tail, suffix): g.group_source_properties() g.group_source_properties(prefix, content, tail, suffix) values( g.to_source_string(), new_g.to_source_string(), ) ```...

It would be useful if definition macros could communicate the defined names in some way. For example, consider a definition macro `pub` that chains to another definition(s) and makes all...

```rhombus module A ~lang rhombus: export namespace Foo module B ~lang rhombus: import parent!A open export def Foo.bar = 42 import: self!A open: rename Foo as Baz self!B open println(Baz.bar)...

Example: ``` #lang rhombus syntax_class HasRepet: kind: ~term | '($elem, ...)' syntax_class WrapsHasRepet: kind: ~term | '$(wrapped :: HasRepet)' let '$(matched :: WrapsHasRepet)' = '(1, 2, 3)' println(matched.wrapped) // allowed...

Fails with an error about `x` defined multiple times: ``` def x :: converting(fun (x :: String) :: Int: x.to_number()) = "1" ``` Incorrectly allowed, since `x` shouldn't be available...

The following syntax class definition: ``` syntax_class Nonsense: kind: ~term fields | '$(term_option_sequence | '~foo')' ``` results in an error within expanded code, instead of some sort of error on...

Consider this code: ``` #lang rhombus/static syntax_class Foo: kind: ~term fields: value | '$(stx :: Number)': field value = stx.unwrap() def '$(foo :: Foo)' = '42' foo.value.unwrap() ``` I would...