File: TODO.md

package info (click to toggle)
react 1.2.0-3
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 1,136 kB
  • ctags: 655
  • sloc: ml: 3,843; makefile: 27
file content (52 lines) | stat: -rw-r--r-- 1,424 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

# Exceptions

* Make steps resistant to exceptions ? There's more than one solution here
  one is to discard the step and unschedule all nodes. Another would be
  to catch them an trap them like in Fut.


# New event combinators

* E.merge but only on simultanous occs ?
* Review Bool.flip init.
* S.Bool.edge,rise,fall plural ?
* E.Bool.flip

# Signal init.

Instead of having bare values why not always have signals ?
This would undermine the temptation of using S.value.

# Stopped nodes

Stopped nodes could be detected and considered as constant by
smart constructors.

# Multisample

Current combinators are not good for sampling multiple signals,
which is generally useful in conjunction with accum. TODO
maybe not in fact see list selector. Just compute the as a signal.
But maybe not always natural ?


# Recursive defs

Investigate the case when dynamics can replace signals with constants
one which could make a direct dep on the delay noded (and hence
raise). Doesn't seem possible but I suspect I saw this once.

# New signal combinators.

To avoid uses of S.value we need better ways to access a
signal's current value and inject it in an efficient
way in the graph.

```ocaml
S.freeze : 'a signal -> 'a signal
(** [freeze s]_{t} = [s]_{t'} where t' is freeze's creation time. *)
```

See if we can return a const and if what happens when used with
bind and/or provide an alternative S.bind for bootstraping.