confirm at this early stage of "lower levels."

I've added core error messages to the standard *lens printer* which checks the concord error state and prints the error tag instead when it occurs. It's not full info, but it's equivalent to printf debugging which at this stage is enough.

Thanks!

4/4

within the concord itself as utf8 strings.

The purpose of this single unit (size_type) style of messaging is for when more elaborate error messaging systems fail. Fallback.

Anyway, all of my test cases print the contents of the concord (as raw numbers) so I can read what's going on and

3/4

The concord data structure holds a single unit (size_type) for error messages. It handles several possible messages, such that the first error that occurs is the only one recorded.

If you want more elaborate debugging messages you can simply inherit existing type *lenses* and write messages

2/4

I almost had the list type working again last night but I ran out of steam.

Today hopefully I can get it done, along with utf8 strings, and the atomic proofs types (comparisons) then I'll be caught up, but with an improved library. Then I post to codeberg.

Thanks!

4/4

so that all objects (be it universes, types, values, expressions, etc.) are properly judgments.

b) I reached a point where I needed to clean up the name space a little.

c) Since I've been overhauling specific types (eg. tuple, cotuple) I've been refactoring and cleaning up code where I can.

3/4

content is located.

The previous design had this too, but the object values were just wrappers around the indices, no reference to the concord directly.

The reason the overhaul is taking so long (over a week now) is for a few reasons:

a) I tweaked the philosophical design a little,

2/4