Ah, I see; I am not an expert in this field so it isn't really clear to me why t... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		turndown on March 30, 2021 \| parent \| context \| favorite \| on: Compiling a Lisp to x86_64 (2020) Ah, I see; I am not an expert in this field so it isn't really clear to me why that information would be needed; the assembly is already being emitted? Is it because functions that will take ints(which will inevitably recieve them from some kind of stack pop or similar) have to have the typing verified before their execution begins? I hope your situation has improved/is improving; good luck! I love your website.

tekknolagi on March 30, 2021 [–]

Well Lisp can reflect on its objects! You can have code like:

(int? foo)

that returns #t or #f depending on if foo is an int. So `int?` needs to have information from somewhere about what type of object it is.

I get more into this in Part 4 (unary primitives).

Thanks :)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact