« first day (686 days earlier)      last day (1089 days later) » 

01:05
ah yes, when attempting to copy vyxal's decompression and decompressing Hello, World! gives you danger, travel!🤣
Apparently This is a test String to decompress. == from is a death retirement to defeltword.
@Seggan I do love travelling dangerously
But death retirement though? Seems like an obvious consequence of dying ngl
Time to fire up PyCharm in what seems like forever and turn on that debugger lol
01:22
Ew, PyCharm
VS Code gang unite!
Let's show those PyCharm users what the best IDE is
i only use vscode for everything except java and python
PyCharm's been finicky enough for me lately that I just switched to VS Code
pycharm is taking up way too much memory tho
Yeah
And unlike Java, the static analysis isn't worth it
python got no static analysis lul
01:23
I have no choice but to use IntelliJ for Java because no other IDE gives such good warnings and errors
agree
@Seggan PyCharm does some static analysis (or linting, whatever you want to call it)
yeah, but it cant tell you that you cant use a list comprehension on a number
Ye
I think there are plugins out there that help
And you can run mypy
This looks promising
interesting
i dont really use python anyway
yet another failed attempt at decompressing Hello, World!: Knew, Next!
3
interesting: Jyxal is reporting an index of 4725, while Vyxal reports 4539
seems to me that my base converter is broken
nope, i had the wrong compression codepage
yay, it works
 
1 hour later…
02:50
\o/
03:15
@user IDLE gang
Because it actually uses an efficient treesitter parser as opposed to whatever VScode python does
 
3 hours later…
06:01
Do we have( or need) a sleep/wait function?
we can add it into date/time digraph
 
3 hours later…
08:41
@user VS CODE
09:27
@user i am neovim gang lol
 
2 hours later…
11:30
@mathcat probably a good idea to bring date discussion here
so far, what I have is:
- element: "¨+"
  name: Add Date and Time
  description: Add a certain amount of time to a date
  arity: 2
  overloads:
    num-num: from_unix_timestamp(lhs) + rhs # rhs = seconds to add
    num-str: from_unix_timestamp(lhs) + seconds(from_iso_format(rhs))
    str-num: from_iso_format(lhs) + seconds(from_unix_timestamp(rhs))
    str-str: from_iso_format(lhs) + seconds(from_iso_format(rhs))
  vectorise: true
but I don't know if that's the most useful way of specifying how much to add
Like, what should the rhs for something like ¨+ be?
@mathcat any ideas?
(the question is open to other people too btw)
do you mean rhs in num-num?
no, in str-str
I am confused
rhs is just the second arg, right?
yes
let me explain what I mean
one of the feature requests in issue #554 is "add/subtract date/time"
but how do you represent time?
and how do you represent how much time to add?
11:38
in the case of add date/time, lhs would have to be a date and rhs would have to be how much time to add
so what's the best way to unambiguously and practically represent time, while remaining useful for a golfing language
that's precisely right
hmm is indeed how I feel about this
my idea was that dates would be using iso formatting
but that doesn't account for how to represent how much time to add
How about time represented like number+abreviation. Eg. 12h23m23s
that way you could leave out eg. minutes and it would still be valid
@lyxal "time ... it is nothing but the interval between 2 events ... in our case time shall always be measured in seconds. now lets consider the time between these 2 events: the big bang and the current time. if we measure this, we get 1¹⁰⁰⁰⁰⁰⁰⁰⁰⁰⁰⁰⁰⁰⁰⁰s, which is isnt a lot." - Alvert Einsteun
ah, Alvert Einsteun
 
2 hours later…
14:16
@AviFS I haven't done much with LazyLists, so I probably can't help you there, but I am really good at breaking stuff and then figuring out what happened, so I'll take a look at it at some point and see what I can find/fix
15:13
@lyxal millis since unix epoch
basically java's System.currentTimeMillis()
or python's int(time.time())
 
4 hours later…
19:43
ya think we should add a way to either import or #include other vyxal files?
 
3 hours later…
Wooo
23:03
🎉
Great work, Seggan!
23:13
for 0.2.0 im planning digraph aliases
@user btw it is far from finished. i only have like 30 or 40 elements
Yeah, but implementing those is more cumbersome than difficult
The real hard work is implementing the bytecode compiler
23:42
@user theres a reason 64 bit integers exist lol
Seggan requested changes on PR #2 (Vyxal/Jyxal): "I'm feeling quite picky today 😉 "
Oh right, currentTimeMillis uses long. I am much relieved now
@VyxalBot Hrmph
Welp, VS Code decided to disappear off my computer so I can't work on it rn lol

« first day (686 days earlier)      last day (1089 days later) »