Project status? tests failing/broken

[Capt0rr]

Hi, really cool project! but running the tests and examples throws all kinds of errors; tried writing something small but stuff was missing or renamed... I gave up. Is there a lot of refactoring or explorative dev happening right now so the tests and examples are out of sync?

[refaktor]

Hi. Yes, there were several bigger changes after a few years of rather stable core language this year. From Capitalization of methods (generic functions), to set-words being split to mod-words for updating (set words now just set the initial value), to everything being const by default and var function. Some functions are also being renamed in trying to better unify the concepts. I rather do this now quickly than drag it out too much.

I am currently going over Meet Rye and Cookbook and updating it (and adding other improvements). I will also have to go over examples/ folder, but I have not yet started that.

Reference (https://ryelang.org/info/base.html) is updated weekly, not with every commit but is generated from passing tests so it's tested. Currently, I am adding docs and tests for it and trying to organize it better. Next update should be today.

This is the related issue, because I got few similar emails to yours after last blogpost. Before not many really looked into Rye so it wasn't an issue.

https://ryelang.org/info/base.html

By tests did you use the tests/ or the info/ folder? Basically all tests now are in info folder. tests is the old way and I am now adding some specific testing to it for tests that are not covered by builtin code / tests / docs by new system (https://ryelang.org/cookbook/improving-rye/one-source/). I should clean the test/ folder up.

If you give me more specific information of what examples are failing or what area you are interested in I can try to speed up those.

I plan to get to a concretely cleaner state in matter of few weeks. Thanks for writing.

Janko

[Capt0rr]

OK great I'll check back later. I started with tests/ then tried info/ - a lot of stuff passed there but had a few failures too so I wasn't sure where exactly the working boundary is.

for now I mostly want to try some terminal scripting and config management.

[refaktor]

To avoid further confusion, I removed old tests (renamed to internal, it's now used for specific internal tests). Renamed info/ to tests/, added a README to folder, so everybody can see how to run tests / docs tool. Added additional tests and worked on them. Not all pass yet.

Now I will move all examples to examples_OLD and start porting them and moving them back one by one. Still a lot of steps to do, but we are moving.

[Capt0rr]

hi @refaktor, finally got a chance to look into this again and immediately got stumped by basic examples from the cookbook/reference:

; Get file information
file: Open %data.txt
info: Stat file
print "File size:" + to-string Size? info
file .Close

seems + is no longer used for strings, I guess join is the only way now? together with the lack of string interpolation this makes working with strings rather clumsy/obtuse, so the above becomes:

print join [ "File size:" to-string Size? info ] ;it's hard to see the forest for the trees here.

prnf and printv and format were misleading too, not at all the analog to printf I expected and limited to one arg? how do you inject multiple args into a string?

rye is generally very compact and elegant so maybe I'm missing something (a lot?) here. Feels like I'm fighting it trying to do very basic stuff.

Might be better to update the front-facing docs before fixing the repo examples.

[refaktor]

Hi @sh4r1k7 ,

+ works only on math now, "++" is for concatenation. I went over website changing this a while ago. I found the wrong example you noticed in Cookbook / Working with / IO. It will be fixed, thanks.

There are 2 more examples of string concatenation on that page using ++. The IO and Email pages are new, and I haven't fully finalized them, hence just a bunch of examples and little text. I will be fixing that soon.

c-like string formatting is not in Rebol/Rye space, but I did add format function because I found it useful. It might not be fully or well implemented, I don't use it normally. I will unify these functions. All Rebol/Rye functions always take the same number of arguments. You can inject multiple values into format by using a block as an argument

[ 123 "hello" ] .format "id: %d msg: %s"

I've unified these with the latest commit.

[Capt0rr]

ah I see. Strangely even AI missed ++, was giving me other weird suggestions like format "{0} {1}", was hoping it would detect the latest changes across the entire doc space, but it seems to have preferred the oldest.

Incidentally your example answered another question I had about the order of args being flipped from regular printf or even other functional langs :).

c-like string formatting is not in Rebol/Rye space

I haven't used Rebol enough to pick up on that - what's the canonical way to format strings?

Thanks for the quick response and fixes, I'll give this another shot - 3rd time's the charm!

[refaktor]

I am preparing document for LLM-s ... that is also the reason I started writing blogpost series (3-4 posts) Learn 20% of Rye in 80% of the time. So I have the basics with examples written down. I get quite good code many times, it changed tons in last couple of months. Before in gemini I would jsut get Python+Rebol mix, now it can explain all Rye code to me well, and most it generates with some fixes even works.

https://ryelang.org/blog/posts/learn_80_rye_in_20_time_code/

The op/pipe words give it some problems and mandatory spacing, so I am experimenting with explanation that would make this click to LLMs. What model / tool were you using?

[Capt0rr]

Kagi's Kimi K2.5, though should've probably used GLM 4.7.

I don't use it normally

What's your normal way of formatting strings then?