Re: [racket-users] Incorrect value/typo in write-resource procedure documentation

It's merged in https://github.com/racket/racket/commit/28a46e36c6f02017d2430b973e0dc8a66b66c94b It's too late for the 8.1 version, but it will be included in the 8.2 version. Gustavo El mié, 14 de abr. de 2021 a la(s) 13:59, Gustavo Massaccesi ( gust...@oma.org.ar) escribió: > Thanks for the re

[racket-users] [Redex] Variable names must be different

Hello, When defining a language, is it possible to define that all instances of a pattern have to be different ? For example, I have f ::= variable-not-otherwise-mentioned, which represents a function name. How do I guarantee all fs are different? Thank you! --Beatriz -- You received this mess

[racket-users] Typed Racket: type relations

Hello Racketeers, working on gradually typing some of my modules I encountered an interesting problem: (define-type Color Fixnum) (: argb-average (-> Color * Color)) (define (argb-average . argbs) (let loop ((as : Fixnum 0) (rs : Fixnum 0) (gs : Fixnum 0)

Re: [racket-users] Variadic fixnum operations (was: Unsafe structs)

On Thu, Apr 15, 2021 at 4:21 PM Dominik Pantůček wrote: > > Hello Racketeers, > > >> * Math/Fixnums/Flonums: All fx+/-/*/... accept two arguments only. No > >> unary fl-, no variadic-argument fl+ or fxior (this one hurt the most). > > > > These definitely became variadic after the type definitions

Re: [racket-users] Variadic fixnum operations (was: Unsafe structs)

Hello Racketeers, >> * Math/Fixnums/Flonums: All fx+/-/*/... accept two arguments only. No >> unary fl-, no variadic-argument fl+ or fxior (this one hurt the most). > > These definitely became variadic after the type definitions were > written, but that's of course not an excuse for not updating

[racket-users] ACM Workshop on Functional Art, Music, Modelling and Design - 2nd Call for Papers, Demos, and Performances

=== 7th ACM SIGPLAN International Workshop on Functional Art, Music, Modelling and Design (FARM) Call for Papers, Demos, and Performance

Re: [racket-users] Wheel / touchpad / trackpoint accuracy/speed scrolling fix for DrRacket

I’ll log the values at different spots and let you know what I find. Clearly, multiplying amt by wheel-scale affects the scrolling behaviour. Somehow this does not affect mouse wheel scrolling une same way. Either the scrolling changes when a different device is used, or the device driver itself

Re: [racket-users] Wheel / touchpad / trackpoint accuracy/speed scrolling fix for DrRacket

Thanks for this summary! But I remain puzzled... As I understand it, `wheel-scale` ends up being 4 on your machine. So removing the multiplication by `wheel-scale` means that `amt` is 1/4 of what it used to be. But `amt` is effectively always divided by `WHEEL_DELTA`, which you've also divided by