Hi, Peter!
> Any reason why supremum-by and infimum-by are not on the "Searching
> sequences" doc page? If you agree I can add these together with supremum
> and infimum.
A link in the help system would be useful, I think. I remember myself
discovering those functions by word of mouth, after having read the
documentation multiple times. It would have been nicer if I read about them in
the help.
> I'll take a look at map-reduce, thanks. I switched from using the factor
> IDE REPL to emacs with Fuel because today I kept creating an infinite
> loop and couldn't break it for the life of me in the IDE. In emacs it
> was C-c C-c. Since I couldn't break it I didn't even know it's an
> infinite loop. That led me to open a file and save the definitions for
> debugging purposes, so I kind of broke my rules at this point. Oh well,
> at least I solved another "day" today, although I'm rather behind at
> this point, not enough time.
If you work in Windows, there is experimental support for C-Break.
Here's how I enable it in my .factor-rc:
! Enable handling of the Ctrl-Break interrupt
USE: listener
t handle-ctrl-break set-global
Only works on Windows, though. There is no such thing as a global hotkey in
Linus, AFAIK.
> Another thing that tricked me:
>
> IN: aoc V{ 1 2 3 } 2 head-slice* 3 suffix! >array .
> { 1 }
> IN: aoc V{ 1 2 3 } rest-slice 3 suffix! >array .
> { 2 3 }
>
> Slices work differently than I expected :) Are there clojure-like data
> structures that are immutable and structurally share most of their
> content?
Not sure about clojure-like. Arrays { } are immutable, while vectors V{ } are
mutable.
You can also have read-only TUPLE: members:
TUPLE: hello-tuple
{ var1 read-only }
{ var2 string read-only }
...
;
---=====---
Александр
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk
