Reference: JuliaLang/julia#38892 (comment)

We accidentally exported HTML and we should warn users to avoid them.

Currently we've implemented a bunch of functions and constraints in a "lazy evaluation" fashion, i.e., whenever we need something for a Style program, we implement it in Penrose. We're getting to the point where we should really have a more complete/comprehensive list (e.g., that users can call at will).

How do we come up with this list? One natural idea is to simply pick some libraries, and

Hi, I'm trying to compile a "Hello World" program on macOs Big Sur 11.0.1 (20B29)

$ ponyc --version
0.38.1-bba16525 [release]
Compiled with: LLVM 9.0.1 -- AppleClang-11.0.3.11030032-x86_64
Defaults: pic=true

but linking fails

Writing ./helloworld.o
Linking ./helloworld
ld: library not found for -lSystem
Error:
unable to link: ld -execute -no_pie -arch x86_64 -macosx_

Current behavior:

.> view ##Nat

  ⚠️
  
  The following names were not found in the codebase. Check your spelling.
    ##Nat

.> names ##Nat

  😶
  
  I couldn't find anything by that name.

.> alias.type ##Nat Nat

  Done.

.> names ##Nat

  Type
  Hash:  ##Nat
  Names: Nat

.> view ##Nat

  -- Nat is built-in.

Desired behavior would be something like:

Motivation

In supercollider/supercollider#4572 we discussed the need for better documentation on when collection functions test on equality vs identity. For instance, SequenceableCollection:indexOf tests on identity, but you wouldn't know it f

Should suppress --strict warnings.