Here’s a random, insane idea: Quickscript competition, but for Racket documentation (or even code examples).

You mean writing quickscripts to help generating doc?

Like select a contract, click on the script, it generates the defproc for you?

I meant a competition in the same manner as Quickscript competition, but no, not related to Quickscript.

Haha, so a Documentation Competition :slightly_smiling_face: @spdegabrielle!

(though I do like the idea of using quickscripts to partly automate the process :stuck_out_tongue: )

@sorawee I think that’s a great idea. The docs are excellent most of the time, but can really need more examples at times. The difficult part to make sure that a large number of people can participate, which means most importantly making doc pull requests extremely easy to make.

@sorawee it is a great idea. I’m all competitioned out at the moment. FWIW there was a #HaskellDocs initiative launched recently https://twitter.com/TechnoEmpress/status/1301133605675184128?s=20

I’m not saying join #HaskellDocs - just that this is another approach.

Tip of the day: #i1/6 is an alternative way of writing the literal 0.16666666666666666

(no excuse for just-deleted comment, I’m even drinking coffee right now :) )

Just for context, 1/6. is not a literal.

Huh? It’s not?

> '1/6 1/6 Looks self-quoted to me

Note the period.

1/6. is an identifier (I believe)

Ohh

(* 6 #i1/6) -> 1.0 So it’s really the reader (as expected)

(define π #i3)

(define π :pie:)

or the more classic (define π #i22/7)

Obligatory pi quote coming up:

The primary purpose of the DATA statement is to give names to constants; instead of referring to pi as 3.141592653589793 at every appearance, the variable PI can be given that value with a DATA statement and used instead of the longer form of the constant. This also simplifies modifying the program, should the value of pi change. -- FORTRAN manual for Xerox Computers

This is beautiful. Written by true physicists I assume.

According to wikiquote (https://en.wikiquote.org/wiki/Fortran#Misquoted), this is a misquote.

> Although this quote appears in different sources[1][2], the real manual does not mention the possibility of changing pi. The real quote is …… This also simplifies modifying the program, if a more accurate value is required.

Thanks for the link. It links to the actual FORTRAN Manual. The first example is:

coding form!

I’m curious why statement numbers are not aligned

Good question.

https://www.reddit.com/r/fortran/comments/ioz8kh/why_are_the_statement_numbers_not_aligned_example/

Let’s see if anyone answers.

72 columns! Bingo!

I just heard this was the origin of the 72 col line length - I have never seen it.

This seems like a very good justification that still applies today :stuck_out_tongue:

ahem

People used to recommend a line width of 80 or 72 column. The number is a historical artifact. It is also a good number for several different reasons: printing code in text mode, displaying code at reasonable font sizes, comparing several different pieces of code on a monitor, and possibly more. So age doesn’t make it incorrect. We regularly read code on monitors that accommodate close to 250 columns, and on occasion, our monitors are even wider. It is time to allow for somewhat more width in exchange for meaningful identifiers.

/ahem

I’m sure I remember reading there were equivalent algorithms to diff trees, and I’m fascinated by the idea of projectional editing. I have auto brackets turned on in DrRacket but my edits don’t always leave me with a valid tree. Also I like the idea that we might be able to make coding easier for people who are sight impaired or sightless.

I’m sure none of this is new; but we have translated interface, why not let Chinese speakers see(定义 where I see (define ?

This reminds me of a project I worked on for Los Alamos 25–30 years ago. I was told there was a team of ~30 PhDs who would code-review a program very very carefully. All I was told was, “This program must never be run, but if it is run, it must run perfectly.” The code review took years, so many years that people on the team rotated constantly, and some died. So the idea was to speed up the code review. I built a tool that instrumented a compiler [GCC] to put everything into a database. That way everyone could look at the code they way they wanted to see it, adjusting colors, etc., renaming things to their preference, while not bothering anyone else’s. It also let them put in annotations that others could read, and mark sections as completed, in progress, approved by so-and-so, etc.

Is anyone making plt-logo masks?

Can Racket CS compile to ARM 64 yet or just 32?

I would :heart: a :racket-flat: mask!!

I half heartedly looked to see if anyone would do custom print masks a couple months ago. I didn’t really find anything economical for a small run iirc.

Halloween?

Obligatory mention of the Indiana Pi Bill https://en.wikipedia.org/wiki/Indiana_Pi_Bill

I’m Australian

We didn’t do Halloween when I was young

Before anyone gets all “ha ha the olds”, may I point out current clamors to give law enforcement an encryption back door.

covid masks

@d_run I think @jesse and @pocmatos have been working on arm64

It works on arm64 now

@d_run

See the 7.8 release notes

amaze

I’m sure none of this is new.

Oh, lol, I was also thinking of Halloween masks for some reason. :)

@spdegabrielle @d_run Matthew stepped in and ended up doing all the work. :slightly_smiling_face: