Stef Joosten

Front-end programming with invariants

2

Ampersand is about programming with invariants, aka constraint-based programming. However, Ampersand rules apply to the back end only. As a front-end programmer used to JavaScript, DOMS, endpoint programming, and the...

Odd behaviour

2

# What happened I ran a reasonably straightforward script on a codespace and in a locally running project template: ```Ampersand CONTEXT Issue1472 PURPOSE CONTEXT Issue1472 {+ There is an error...

# What happened I wrote a prototype to execute in Codespace from the project-template repo. All went well, but the fourth or fifth deployment. All of a sudden the prototype...

Generating prototypes from Atlas population

5

**Is your feature request related to a problem? Please describe.** Simon's research is about using the Atlas as an editor, so users can edit scripts without knowing the Ampersand syntax....

Semantics of INCLUDE (this has to do with namespaces)

2

# Problem Namespaces require semantics that will prepare us to work with distributed systems and allow us to do data migrations. So far, we have generated information systems with one...

feature: Name spaces

12

@Michiel-s, @stefjoosten , and @hanjoosten have discussed an implementation of the multi-context functionality. We have agreed on the following: 1. A pattern is a namespace, so we'll drop the keyword...

Missing feature in Haskell's Excel importer

1

# What happened Ampersand-v5.0.0 [feature/labels-in-ADL-files:662580d51] produces no compile-time errors nor warnings when compiling this script: ```Ampersand CONTEXT Issue1465Test IN DUTCH CLASSIFY Auto ISA Voertuig RELATION eigenaar [Voertuig * Persoon] [UNI,TOT]...

PrototypeContext.adl does not compile

1

# What happened I tried to compile the AmpersandData/PrototypeContext/PrototypeContext.adl` code with the Ampersand-v5.0.0 compiler, expecting it to compile stand-alone. This code is used to generate prototypes, so I know apriori...

Compile time restrictions w.r.t SESSION

3

# What happened I got a run time error message immediately after deploying a script: I was surprised because the compiler found my script correct and yet its deployment produces...

# What happened I noticed that ```Ampersand RELATION r[A*B] ENFORCE r := I[A]#"foo" ``` has a different semantics than ```Ampersand RELATION r[A*B] ENFORCE r := V[A*B]#"foo" ``` If I test...