Re: [Factor-talk] Compiler

OK, thanks. — don > On Aug 24, 2021, at 14:53, John Benediktsson wrote: > > Probably 2022. > > On Tue, Aug 24, 2021 at 2:33 PM dgpdx > wrote: > I’d love to use factor. Any idea when the port to arm64 will be completed? > — > don > > >> On Aug 24, 2021, at 14:29

Re: [Factor-talk] Compiler

Probably 2022. On Tue, Aug 24, 2021 at 2:33 PM dgpdx wrote: > I’d love to use factor. Any idea when the port to arm64 will be completed? > — > don > > > On Aug 24, 2021, at 14:29, John Benediktsson wrote: > > Contributions are welcome! > > (Also questions, if you have any.) > > On Tue, Aug 24,

Re: [Factor-talk] Compiler

I’d love to use factor. Any idea when the port to arm64 will be completed? — don > On Aug 24, 2021, at 14:29, John Benediktsson wrote: > > Contributions are welcome! > > (Also questions, if you have any.) > > On Tue, Aug 24, 2021 at 2:17 PM George Cherevichenko > mailto:george.chereviche..

Re: [Factor-talk] Compiler

Contributions are welcome! (Also questions, if you have any.) On Tue, Aug 24, 2021 at 2:17 PM George Cherevichenko < george.chereviche...@gmail.com> wrote: > Thank you. I think, I understand stack-checker now. The problem > (stack-effect checking) is very close to "typization" in lambda-calculi,

Re: [Factor-talk] Compiler

Thank you. I think, I understand stack-checker now. The problem (stack-effect checking) is very close to "typization" in lambda-calculi, but Pestov set types to "loop" and "while". I'll think about it:) вт, 24 авг. 2021 г. в 21:59, John Benediktsson : > You can see some curry declared and then de

Re: [Factor-talk] Compiler

You can see some curry declared and then defined as part of bootstrap in: https://github.com/factor/factor/blob/master/core/bootstrap/primitives.factor#L289 On Wed, Aug 18, 2021 at 3:01 PM George Cherevichenko < george.chereviche...@gmail.com> wrote: > Hi > Where are definitions of "curry" and

Re: [Factor-talk] Compiler

Yes, "namespaces:set" is the word "set" from the vocab "namespaces"! To distinguish it from the word "sets:set". Logic is our power. чт, 19 авг. 2021 г. в 01:00, George Cherevichenko < george.chereviche...@gmail.com>: > Hi > Where are definitions of "curry" and "compose"? I can't find them in > k

[Factor-talk] Compiler

Hi Where are definitions of "curry" and "compose"? I can't find them in kernel.factor Is it a trick of compiler? For example, "dip" is defined as : dip ( x quot -- x ) swap [ call ] dip ; "because the compiler special-cases them". What is "namespaces:set" in compiler.factor? ___

Re: [Factor-talk] Compiler error in fuel.factor

"Slava Pestov" writes: > Jose, > > This word has an unbalanced branches error: > > : (fuel-word-def) ( name -- str ) > fuel-find-word > [ [ def>> pprint ] with-string-writer ] when* ; > > Indeed, if fuel-find-word returns f, then the word leaves nothing on > the stack. What you want is to

[Factor-talk] Compiler error in fuel.factor

Jose, This word has an unbalanced branches error: : (fuel-word-def) ( name -- str ) fuel-find-word [ [ def>> pprint ] with-string-writer ] when* ; Indeed, if fuel-find-word returns f, then the word leaves nothing on the stack. What you want is to put the with-string-writer outside of the

Re: [Factor-talk] Compiler error in libs/vars

There's no error, Ed, you just wrote your code wrong. Set takes two things, and each provides one, so there *is* an unbalanced branch. Each, deep in its implementation, uses (repeat), and the compiler is just showing you that. That's where the actual unbalanced branch takes place, since it is all i

[Factor-talk] Compiler error in libs/vars

Slava, I get a compiler error when loading libs/vars. It complains about unbalanced branches in (repeat) and the call chain goes up to let. But let never calls that word directly. It get's there from each. Do you know what's going on? Paste this into the listener: : let ( vars body -- result )