The Garbage Collector

« first day (145 days earlier) ← previous day next day → last day (365 days later) »

Redz

12:42 AM

i love pandas

there could not be a better python library for scatterplots

Seggan

12:52 AM

Me: implements a potential bugfix
My computer: now produces another error for the same situation
Me: good enough

Seggan

1:24 AM

rate my syntax:

fn read_line()
    let result = string.builder()
    let c = io.stdin:read()
    while c != 10 and c != null
        result:append(c:char())
        c = io.stdin:read()
    end
    return str(result)
end

Eldritch Conundrum

1:34 AM

I would have rather expected io:stdin.read(), if these are namespace & call

Redz

@Seggan wouldn't that mean you just created a different problem that overwrote the original one

1 hour later…

lyxal

2:47 AM

just made a recursive factorial program compile in that language with the Out << syntax

:sunglasses:

Redz

3:16 AM

clapclapclap

lyxal

so fun fact

the stack assembly architecture the course uses has the following op:

41 LB 1 x Instr Byte push 8-bits, sign extended to 64, as INTG

and the intention is that it pushes a number represented by 8 bits to the stack

meaning you'd expect a range of -127 to 127

however, decompiling the assembly simulator jar shows it's implemented as

if (this.offset > 127) {
                this.offset -= 256;
            }

Meaning that technically speaking you can use LB to load any value, even values bigger than a byte

e.g. LB 42325 loads 42069, despite the fact it's 16 bits, not 8

good fun :p

9 hours later…

lyxal

12:00 PM

Q: Best practice for if-elif-else statements

What is considered better practice? Case 1: if n == 0: doThis() elif n < 0: doThat() elif n > 0: doSomethingElse() Case 2: if n == 0: doThis() elif n < 0: doThat() else: doSomethingElse() The first case is more explicit and (arguably) clearer. The second case doesn't han...

I was wondering why it hadn't been closed for bike shedding until I realised that's one of our close reasons here :p

Seggan

12:30 PM

@EldritchConundrum no it's Lua style: io is a table, the colon is a call with self

2 hours later…

Seggan

2:57 PM

@Redz shh, we don't talk about that

9 hours later…

Redz

11:38 PM

wahahaha

my math teacher today was like 'ok guys we need to learn some python basics for this test coming up' and i got detention for laughing in class

Ginger

hey @lyxal do you pronounce @Redz's name "Redzed"

lyxal

"reds"

Ginger

mmm

your loss

lyxal

What does my rendition of an internet web comic meme have to do with anything?

Ginger

nothing, I just wanted to reference it

(love the clown)

lyxal

11:46 PM

@Ginger gasp

How could you say such a thing?!?

I thought you were a [BIG SHOT]

Ginger

wrong clown, doofus

that [[Around Town]] barely [Jesters] at all

user

@Redz Are you Indian, by any chance?

Because that sounds like a very Indian thing to do

Does anyone know of any statically typed Lisps with a type system as advanced, as, say, Java's?

(I don't mean typed Racket and Clojure, I mean a Lisp that was meant to be statically typed from the start)

Seggan

come ON

i spent 2 hours messing with my metatable lookup functions to fix an error only to realize i forgot my own operator precedence and an extra set of parens was all i needed

« first day (145 days earlier) ← previous day next day → last day (365 days later) »

all rooms