hi… hoping someone has a quick snippet to create a pict
of a Post-It note with a curled (or even square dog-ear). I’m under a little bit of time pressure (and away from the racket docs, TBH), but if nobody has one immediately at hand, I could write one.
Super quick, using shadow frame (so not exactly what you want I guess).
oh… it’s effective enough. thanks
when i say dog-eared, i want the impression that it was stuck onto the slide in a hurry
which this does.
thanks larent
Laurent
perhaps some new Chez tagging optimizations: https://weinholt.se/articles/design-low-tagging-z3py/
That looks awesome
what about tracking purity?
I think that’s much harder — the suggestions in the post are things that could be added without much change to existing Chez code
Is anyone familiar with a “taxonomy of abstraction levels” especially with regards to computer execution.
Intuitivily a language like python is more abstract than assembly, and assembly is more abstract than machine code, etc etc.
In particular I’m interested in defining/describing the actual “abstraction” rather than how abstract different programming languages are
quick question, im trying to run a script with gracket <filename>
but it makes the OS focus on an already opened script in the same way. Is this a limitation? Do i have to use raco to make executables if i wish to have multiple scripts openend? Edit: I read more, and I think I want to run my script with racket but with no console, is that possible?
Is it possible to require a typed/racket module into (untyped) racket without contracts?
That requires cooperation with the typed module I think? I was trying to make a simulation that used math/distributions
and it was very very very slow.
You can define your own typed module, and then provide what you need with unsafe-provide
Aha that makes sense now. Thanks!
should there be something like (require (unsafe-typed-in foo x y z))
for this?
Totally forgot about live-free-or-die
@shriram gave a great PapersWeLove talk https://www.youtube.com/watch?v=43XaZEn2aLc
how do i resolve a relative path to an absolute path? using (build-path 'up "out")
which produces #<path:../out>
.. i need absolute path
nevermind, (path->complete-path)