Skip to content
HN On Hacker News ↗

Rhombus v1.1

▲ 95 points 28 comments by spdegabrielle 11h ago HN discussion ↗

Pangram verdict · v3.3

We believe that this entire text is human-written.

0 %

AI likelihood · overall

Human
100% human-written 0% AI-generated
SEGMENTS · HUMAN 1 of 1
SEGMENTS · AI 0 of 1
WORD COUNT 256
PEAK AI % 0% · §1
Analyzed
Aug 17
backend: pangram/v3.3
Segments scanned
1 windows
avg 256 words each
Distribution
100 / 0%
human / AI fraction
Verdict
Human
Pangram v3.3

Article text · 256 words · 1 segments analyzed

Human AI-generated
§1 Human · 0%

Rhombus version 1.1 is now available! We are pleased to announce Rhombus 1.1 is now available from https://rhombus-lang.org/. Rhombus is a general-purpose programming language that is easy to use and uniquely customizable. As of this release: Add annot and annot.def as ways to define an annotation without directly writing meta-time (i.e., macro) code. Add as as a binding form, which is sometimes more readable for naming than using && and provides a way to shadow an identifier that is bound as a binding form. Change class to bind inherited names using the corresponding superclass or interface reference. Change space.enforest to adjust scopes in the same way as for a macro transformer when applying an identifier handler. ffi: Add an initialized-array variant of new. pict: Change explain_anim to add a ~label_as argument. Change Pict.rebuilt to replace as rebuilt, and also add a ~as_rebuilt argument to select the old or new bevavior. The Pict.rebuild method also supports ~as_rebuilt. Improve magic_move and cross_fade to better handle paragraph points and multiple instances of a child pict. slideshow: Add slide_transition and continued page numbering. Thank you to community members who contributed this release. Feedback Welcome Questions and discussion welcome at the Racket community on Discourse or Discord (#rhombus channel) Anyone can participate in Rhombus design discussions. The Racket team’s unofficial motto is anything we can do, you can do: programmers should feel empowered to participate in the creation of the languages they use. Discussions, pull requests, and issues are open to all, and a wide variety of perspectives is especially beneficial.