Support batches of synchronous operations

As originally discussed in #5, the JS proxy does not allow non-asynchronous overriding of = and delete. However, we could still make use of them by introducing the concept of batched operations.

Syntactical sugar

Some syntactical sugar for updates and deletes.

Update

data.user.name = 'Ruben';

Translation:

path.addPendingPromise(user.name.delete()) // This will have no effect if no previous value existed.
path.addPendingPromise(user.name.add('Ruben'))

(@RubenVerborgh You’ve mentioned before that you don’t like the addPendingPromise, any other suggestions?)

data.pending is an awaitable over all pending promises.

Delete

delete data.user.daughter;

Translation:

path.addPendingPromise(data.user.daughter.delete())

Batching

Batching allows multiple operations to be grouped together in a single SPARQL query, for improved efficiency.

// Do data things batched
data.batch((batch) -> {
  batch.user.name = 'Ruben';
  batch.user.brother.name = 'Niels';
  batch.user.sister.name = 'Muriel';
  delete batch.user.daughter;
});

[RubenVerborgh]

(@RubenVerborgh You’ve mentioned before that you don’t like the addPendingPromise, any other suggestions?)

.schedule

[rubensworks]

For reference: WeakRef has just been introduced: https://v8.dev/features/weak-references This would allow scope detection and help simplify batching operations.