sorawee
2019-11-11 10:22:58

Are there examples of solutions to the expression problem in Racket?



spdegabrielle
2019-11-11 13:13:31

What’s everyone working on this week (46/2019)? https://groups.google.com/forum/#!topic/racket-users/_3mTn5aa9UU New week, new Racket! What are you folks up to? Answer here, racket-users or at /r/racket !



spdegabrielle
2019-11-11 13:15:03

(shamelessly copied from r/rust)


spdegabrielle
2019-11-11 18:48:16

capfredf
2019-11-11 19:15:38

Hi @mflatt, Is it intentional that a built-in struct property accessor , e.g. custom-write-accessor, doesn’t pass struct-type-property-accessor-procedure??


mflatt
2019-11-11 19:18:10

No. That looks like a bug in the construction of custom-write-accessor and similar in non-CS Racket.


capfredf
2019-11-11 19:19:39

Got you.


sorawee
2019-11-12 00:18:12

How do I find if the current machine is x86 or not?


sorawee
2019-11-12 00:19:21

(system-type 'machine) seems to do it, but it seems very difficult to parse


samdphillips
2019-11-12 00:28:17

On my Windows system it does not seem to indicate CPU arch > (system-type 'machine) "Windows NT 10.0 (Build 18362)"


jaz
2019-11-12 00:57:59

(system-library-subpath) should have the arch, but there isn’t an ideal function for this.


notjack
2019-11-12 01:15:20

Beware that there isn’t really a standardized list of architecture names


notjack
2019-11-12 01:18:01

The closest thing to that is the name registry used by Go in the $GOARCH environment variable. That list is a de facto standard because the spec for Docker images references it (because most of Docker was built in Go).


jaz
2019-11-12 01:20:27

The arch specifiers provided by (system-library-subpath) are chosen by racket; they’re not reported by the OS.


jaz
2019-11-12 01:23:32

@sorawee you can look for x86_64 or i386 in the result