Vyxal

user

00:34

@emanresuA I don't think so

Feel free to take over, I'm going to be busy the next few days so I don't think I'll be able to work on it :(

emanresu A

I'm trying to get DSO to be usable

So I won't be doing much work either

user

:(

Hope DSO goes well, would be very nice

emanresu A

01:41

It's just going to be stuff like risky, K, ngn/apl, deadfish etc.

Mayyybe scala2js if I can configure it

emanresu A

03:29

→ 12 messages moved to Trash

lyxal

12:28

Tomorrow, element planning for version 3 starts

@user when you have the chance/opportunity to do so, would you be able to give a brief guide on how you recommend setting up VyxalS locally?

I think that'd help the majority of people here who might not necessarily know how to establish a Scala project

PyGamer0

why are we using scala again?

lets use haskell or rust :p

or c++

lyxal

@PyGamer0 because Scala is good

And it can also transpile to JS

Meaning that online interpreter hosting could just be done on github pages

@PyGamer0 And also we're using Scala because I actually want us to finish v3 some time in the next decade

PyGamer0

@lyxal lol

user

13:05

@lyxal I’d be glad to, writing guides is easier than writing code :p

mathcat

13:21

@lyxal scala?

for what?

lyxal

For version 3 of vyxal

Anyhow I gots to go for sleep

Goodnight vyxalers

o/

mathcat

o/

wait WHAT

version 3 is going to be coded in Scala not python?

from hyper-neutrino:

RUSH F

►

PyGamer0

13:37

@mathcat i wouldn't say coded, to me it sounds veey weird

lol

mathcat

but wait really?

PyGamer0

yes

mathcat

a rewrite of vyxal in scala?

PyGamer0

yes

mathcat

ok lemme learn scala

PyGamer0

13:38

no

/s

mathcat

?

and why Scala?

PyGamer0

scrolla bit up

i asked the same thing

cause i forgot

and im pretty sure scala is not imperative

i think its functional

mathcat

oh nice

@PyGamer0 what's that?

PyGamer0

@mathcat a different programming paradigm

mathcat

I'm still not understanding.

PyGamer0

13:44

en.m.wikipedia.org/wiki/Programming_paradigm

mathcat

lemme just learn scala, maybe I'll understand then

user

14:12

CMA: If y'all try out Scala and don't like it/don't like it as much as Python, we can always stick with Python. I don't want to force y'all to do something and then have people leave Vyxal because of that

mathcat

user

lol

Razetime

14:31

@user however i will be disappointed and I will shame you for going away from scala

user

:(

@user I take this back, y'all MUST learn Scala or I'll nuke your fridges to avoid being ostracized by Razetime

mathcat

NO

everything but not that

I have butter in my fridge

mercy please

user

Oh okay I'll nuke your microwave then

mathcat

better thanks

PyGamer0

15:06

@user NO I have milk in my fridge

that can be converted to butter

@user let me go quickly read a bunch of scala stuff

ah scala has OOP and is functional

@user i think i like scala, now that i read some things

Fmbalbuena

@PyGamer0 Is there a way to join every element like (`1`|`1`|`1`) and `0` gives (`10`|`10`|`10`)

Aaroneous Miller

+

!!/run (`1`|`1`|`1`) `0` +

Vyxal Bot

@AaroneousMiller 00

Fmbalbuena

@AaroneousMiller ~~OMG THANK YOU VERY MUCH!!!!!~~ Nope

Aaroneous Miller

@VyxalBot wat

PyGamer0

15:14

@Fmbalbuena ok let me tell you something: I am not very good at vyxal

Fmbalbuena

@AaroneousMiller you need swap

PyGamer0

@AaroneousMiller shouldnt you use chevrons?

Fmbalbuena

!!/run (`1`|`1`|`1`) `0`$ +

Vyxal Bot

@Fmbalbuena 00

Aaroneous Miller

@PyGamer0 oh lol yeah I just copied from fmbalbuena's message

Fmbalbuena

15:15

@AaroneousMiller which?

PyGamer0

!!/run ⟨`1`|`1`|`1`⟩`0`+

Vyxal Bot

@PyGamer0 ⟨ `10` | `10` | `10` ⟩

PyGamer0

@Fmbalbuena ^

Aaroneous Miller

⟨⟩ != ()

PyGamer0

^

similarly TNB ≠ TAO :p

Fmbalbuena

15:17

@AaroneousMiller because I can't use ⟨⟩

@PyGamer0 but I can use this

PyGamer0

@Fmbalbuena use Adám's Vyxal LB then

Fmbalbuena

!!/run Adám's Vyxal LB then

Vyxal Bot

@Fmbalbuena ⟨ ⟩

Fmbalbuena

@PyGamer0 Thank you

Aaroneous Miller

15:30

@Fmbalbuena You can also use the onscreen keyboard on the Vyxal online interpreter

Fmbalbuena

@AaroneousMiller I'm already using.

user

@PyGamer0 :)

@lyxal Added a little to the readme, I'll write more when I can

user

18:33

I wish lambdas worked on the global stack and functions worked on local stacks in Vyxal :(

Aaroneous Miller

We could introduce a flag or smth to indicate whether it's using the global stack or local stack

Actually, i've got a better idea

We are going to change full-stack elements to have an arity of -1 to indicate that they're using the whole stack, we could make it so that lambdas can also have an arity of -1 which would make them use the stack

user

Ooh that'd be nice

@AaroneousMiller We'd still have to implement global stack functions and local stack lambdas tho :(

I don't particularly care about it from a language user perspective, I just want it to be easy to implement :P

Aaroneous Miller

call it a v3 feature

user

lol

Aaroneous Miller

re: the -1 arity thing; since we can already use d (double) and T (triple) to set the arity to 2 or 3, we should also be able to do the same thing with N (negate) to set it to -1

user

18:47

+1

Aaroneous Miller

no, we want the arity to be -1, not +1 :p

user

-1 >:|

Aaroneous Miller

lol

user

19:07

@AaroneousMiller Wait actually @lyxal and everyone else would y'all be okay with this as a serious thing?

emanresu A

Sure

user

I should probably make this a discussion

emanresu A

I had an additional feature request: prepending : or D to the body of a lambda sets its arity to 2 / 3

user

How would you distinguish that from wanting to execute :?

Also, we can just put d and T at the end, right?

emanresu A

Oh wait, true...

Never mind

user

19:18

Proposed the lambda global stack thing here

user

19:29

!!/hyperping

Vyxal Bot

@AaronMiller @AaroneousMiller @Allxy @Ausername @Milk @PyGamer0 @Wansen @astonearachnid @emanresuA @grandBagel @hyper-neutrino @lyxal @math @pxeger @rues ^

user

Because why not

(but seriously, this would be a big-ish change and it would be good if everyone saw and voted on it

lyxal

23:26

@user but the moment you do that, you lose the ability to re-use the lambda's argument if there's nothing on the stack

user

Oh

How often is that needed?

lyxal

lambdas using global stack by default is one of the things I never liked about 05AB1E

@user very often

user

Oh boy

lyxal

good idea for a flag, not so much for default behaviour

I was thinking that maybe there could be something that pops the top of the global stack and pushes it inside a lambda

1 2 3 λ¿+; -> pops the 3 as the lambda's argument, ¿ pops the 2 from the global stack and returns 2 + 3

that is, for example

2

A: Sort every dimension

Vyxal, 6 bytes λ-[vxs Try it Online! -5 thanks to @emanresuA in vychat Explained λ-[vxs λ # a lambda that takes a single argument n and: - # subtracts n from itself (scalars return 0 which is falsey, lists return a list of 0s which is truthy) - borrowed from https://codegolf.stackexc...

7

A: How many times can I skip a stone?

Vyxal G, 20 16 bytes żƛ{D?L<|?i+1$}!⇩ Try it Online! This feels too long That's better. Explained żƛ{D?L<|?i+1$}!⇩ ż # The range [1, len(input)] - this represents all possible starting throw lengths ƛ # over each item N in that range: {D?L<| # while t...

user

Ah

lyxal

23:30

and that's just from the most recent vyxal answers

user

Aight, guess we'll have to keep the arities D:

lyxal

lambdas are one of the things I've thought about at length

so I ask that you trust me when I say that having arities is a good idea

user

Also, how do you apply transformers when you want auto-closing to work? Would you be able to do λ...v to vectorise the lambda? (I assume not, because v would be applied to the last element of the lambda and not the lambda itself)

lyxal

That's one of the things I've'n't thought about at length

user

lol

I actually like the fact that modifiers currently work backwards like APL, because it's kinda more clear that they're not normal functions, they're operating on the elements themselves

~~It's also easier to parse modifiers the way I've started implementing it and I don't want it to become harder~~

lyxal

23:35

would it be a bad idea to have both prefix and postfix operators?

user

It depends on what those operators are

lyxal

because there's some postfix operators that I'd think would be useful

like for example, capture everything to the start of the line as a lambda

user

What benefits do postfix operators have?

@lyxal oic

lyxal

they can scan backwards and collect elements until a condition is met

emanresu A

You can just pop tokens from a stack

^^ pretty much

lyxal

23:37

@user or capture everything to the previous lambda as a lambda

or capture everything to the previous modifier/transformer as a lambda

user

@emanresuA See I'm not using a stack in the Scala impl and I'm too lazy to add it

But aight I'll modify the parser to handle postfix

lyxal

but transformers and auto-closing probably means that all the stuff like reduce/vectorise/etc will have to remain prefix

user

So we stay with prefix for all modifiers except for the capture everything to the previous line/lambda ones?

lyxal

I suppose so

I guess postfix stuff is good for tacit langs where things join together implicitly

Transcript for