@omenos @tristan957
Hey, that's great to hear.
The Hare team are also discussing quarterly versioned releases -- 0.YY.Q (e.g. 0.24.0) ‐- which might make things easier.
https://lists.sr.ht/~sircmpwn/hare-rfc/%3CCXHZO8WYRECI.180RNPAOI7G1T%40taiga%3E
@latenightowl
Send a bug report to the hare-users mailing list
https://harelang.org/community/ -> hare-users archives
Hey @fkinoshita
Check out this idiomatic cat(1) implementation from hautils, a collection of POSIX utilities written in Hare.
https://git.sr.ht/~sircmpwn/hautils/tree/master/item/cat.ha
Hi @tristan957,
It's up to Fedora, but I don't see that happening soon since Hare does not have a steady version release cycle yet.
I help maintain upstream #harelang.
@lanodan
Yeah
@lanodan
The name was my idea, to "reckon through a chronology" as opposed to just a univariable timescale (date::add()). You "reckon" since sometimes you don't know where you'll land if at all, due to a timezone discrepancy or field overflow (something we're still working on).
In my research, most stdlibs unify it all into one "Add()" function, a verb which doesn't sufficiently hint at what is essentially a complex vector operation (<Y,M,D...> + <Y,M,D...>). Time will tell (heh) if we made a good design choice.
Also, nods to @vladh for helping with the implementation.
@drewdevault
Crazy idea, what about an `next` builtin?
i=0
next i # i == 1
next i 5 # i == 6
next i -2 # i == 4
x=0x0F
next x # x == 0x10
s=the
next s # s == thf
@drewdevault
Improvement:
tr -dc '[:alnum:]' </dev/urandom | head -c 64
Libre software engineer with physics background.
Maintainer for @hare date/time.
.py .go .ha ...
en es ...
\t <dl> agpl posix 9p