Daniel Chao

Type parameters in `new Mapping<TypeA, TypeB>`/ `new Listing<Type>` are not checked

3

This does not throw, but should: ``` foo = new Listing { "hello" } ``` In the below, both types should be checked: ``` foo: Listing = new Listing 5)>...

Repro steps: Check out this commit: https://github.com/rnapier/pkl-pantry/commit/ce6b87c0568636290bb86b624bcd137d367de511 Then bump version on `pkl.experimental.uri`, then run `pkl project resolve packages/*/`

Make EvalTask track resolved output paths

7

This makes Gradle track `getOutputPaths()` and `getMultipleFileOutputPaths`. These represent the actual outputs of the EvalTask.

Type checking a mapping/listing should be lazy

2

Currently, accessing a property of type `Mapping` or `Listing` will shallow-force the whole mapping/listing. The shallow-force gets skipped if the type is `unknown` or `Any` (e.g. `Listing`, or `Listing`, or...

For generators are eager in values, but should be lazy

1

```groovy x = new { ["one"] = 1 ["two"] = this["one"] + 1 } y = (x) { for (k, v in x) { [k] = v + 1 }...

Further down the line stuff

1

1. Set up a system that lets users call each other without revealing phone numbers 2. Set up confirmation that the phone number actually is their phone number. 3. We...

These should be get requests, and this means that the server will need to keep track of which parker is picking up which rider.

Right now, going to #/rider/coming/:uid, with any valid UID, will bring you to a page saying that user (as long as it's a valid UID) is coming to get you....

This also means the schema needs to change