@lexi.lambda yes, that’s right. (Ie, it does get annotated, but the “stack” that is returned doesn’t have that mark anymore, to preserve proper space behavior of the implementation)

Hey, could anyone confirm that the racket C- source is purely C99

Yes, it’s C99, except for occasional bits of inline assembly or GCC-specific features that are guarded by pre-processor conditionals

Mm hmm, thanks:+1:

@robby: Makes sense. Does that mean (values x) is not equivalent to x in tail position, and the optimizer can’t replace the former with the latter?

@lexi.lambda it can only do that transformation if the tail difference is not relevant

Sad day, the Valentine racket heart is still the old logo.

lol, today is the “Racket logo memorial day”

lol, love it.

@leif Is that why twitter thinks the logo is “sensitive material”?

@asumu He he he….ya. Its too risqué….can’t show anything besides the newest logo

@lexi.lambda correct.

@lexi.lambda (of course if x is just a variable, then it is safe, but if x is some expression (that might use current-continuation-marks) then it is not safe)