Replies: 8 comments 32 replies
-
TransformersThese are going to replace the current system of modifiers. The only difference is that transformers will be postfix like Jelly's quicks instead of prefix. |
Beta Was this translation helpful? Give feedback.
-
|
correct. That's one of the core features of Vyxal anyway. |
Beta Was this translation helpful? Give feedback.
-
|
A deep vectorise quick (vectorise all the way down). |
Beta Was this translation helpful? Give feedback.
-
|
Wait so wouldn't this be less golfy because you wouldn't be able to take advantage of auto-closing strings/structures? |
Beta Was this translation helpful? Give feedback.
-
|
(also minor note but prefix is actually easier to parse the way the Scala implementation of Vyxal is done right now lol (granted, it's not safe from stack overflows with really really huge programs)) |
Beta Was this translation helpful? Give feedback.
-
|
Will we have one main closing character or will we stick with all of |
Beta Was this translation helpful? Give feedback.
-
General Element RequestsReply to this with any general element requests you'd like. They don't have to be specific with type overloads, just general ideas/summaries of what you think would make Vyxal golfier. |
Beta Was this translation helpful? Give feedback.
-
|
Not very well... |
Beta Was this translation helpful? Give feedback.
-
|
@pxeger what do you mean? sympy's imaginary number system is used, and |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
There's still a lot of optimising to do in terms of usability. Factorial of a complex number should use the gamma function. What happens when you compare complex numbers? I dunno. |
Beta Was this translation helpful? Give feedback.
-
|
What about an element that transforms a string to match case with another? For example |
Beta Was this translation helpful? Give feedback.
-
Better English compressionWhile our string compression is fine for stuff with words and other symbols, it's substantially worse than say Jelly's for plain english. |
Beta Was this translation helpful? Give feedback.
-
|
I have managed to copy Jelly's compression for a now-obsolete language I was writing, we can use that. As long as the license allows it, of course. |
Beta Was this translation helpful? Give feedback.
-
Jelly's MIT licensed, Vyxal's MIT licensed. No problemo. |
Beta Was this translation helpful? Give feedback.
-
|
Here are a few patterns which can't easily be shrunk with new additions the way Vyxal currently works. I think these could be dealt with using the transformer systems:
|
Beta Was this translation helpful? Give feedback.
-
|
Having lambdas operate on the global stack and functions on their own local stacks would be really nice. You wouldn't have to keep track of the arity of every lambda and element (you'd still to have keep track of function arities but that's much more manageable). Lambdas are also written right where they're applied, meaning that you're aware of what the global stack looks like at that point and can work right there. Functions are written elsewhere, so you have no idea what the global stack will be like when you run a function. Of course, we could always have a flag to make functions work on the global stack, but not to make lambdas work on local stacks. |
Beta Was this translation helpful? Give feedback.
-
|
How about a global lambda structure instead? Local stack lambdas allow for argument reuse to happen and means that you can remove instances of |
Beta Was this translation helpful? Give feedback.
-
|
NO. Lambdas are functions, they should stay that way .It's much more sensible for argument reuse anyway. |
Beta Was this translation helpful? Give feedback.
-
digraph to output a string, coloredsuch a digraph might take |
Beta Was this translation helpful? Give feedback.
-
|
This won't make sense on online interpreters though |
Beta Was this translation helpful? Give feedback.
-
|
naz's online interpreter uses |
Beta Was this translation helpful? Give feedback.
-
|
There are libraries to automatically convert ANSI coloured text to HTML markup. Even full terminal support could be emulated using xterm.js |
Beta Was this translation helpful? Give feedback.
-
|
Also, there's an |
Beta Was this translation helpful? Give feedback.
-
|
Probably just `;` for golfiness.
…On Tue, Apr 26, 2022 at 8:27 AM Steffan ***@***.***> wrote:
Will we have one main closing character or will we stick with all of ;)]}?
—
Reply to this email directly, view it on GitHub
<#551 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APABUG5I3Q3AY7J4GPFIGDTVG3535ANCNFSM5LB6HH2A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Based on the current YAML, it's |
Beta Was this translation helpful? Give feedback.
-
Slight lambda improvementMaybe a regular lambda could apply to the next four elements if no closing semicolon is found for the lambda? |
Beta Was this translation helpful? Give feedback.
-
This is for planning what Vyxal 3.x will look like. Unlike usual feature request issues, you have the chance to completely reshape the language here (within reason).
Some things to note:
Other than that, everything is open to consideration. Think outside the box. Come up with the wildest/unique ideas you can.
I'd ask that you keep it to one suggestion per reply
Beta Was this translation helpful? Give feedback.
All reactions