it's a bug, or something like that could be possible and acceptable?

Hi @U0BBFDED7, could you share the snippets of it.. im so far never seen/goes to that error

this error pops up when you try to use signal / stream outside the reactive context

When I'm at the computer, I'll make a gist

signals and streams must be bound to a reactor instance, therefore they must be constructed in reaction to a reactor event. To create a new signal in reaction to an arbitrary event, the event producer itself must be a signal or a stream.

@leonoel I generally have this and it works, but in one particular case it crashes if I have sleep in ap

but I can't reproduce it on a smaller example, so I probably have a bug somewhere

it works, it's awesome, the problem as usual is on my side

is this normal behaviour and something to get used to, or is there a chance of improvement here?

test source file is 90kb, after compilation it is 120kb

for comparison, using core.async increases the size to 100kb

and using pure js promises makes the resulting file only 60kb.

> Probably due to the macros in cloroutine. Yes. code generated by cloroutine is verbose and probably not very closure compiler friendly > is this normal behaviour and something to get used to, or is there a chance of improvement here? The size increase is inevitable due to the additional machinery required, but I think there's room for improvement. Various optimizations could be added to cloroutine that could improve both runtime performance and code size, it's been low priority so far but I'm definitely interested moving in this direction

@U0BBFDED7 So we can understand, can you describe what exactly the problem you see in production with core.async js build size?

I.e. what exactly is the harm being done

each use of go increases the buildsize by about 1kb

we have used go 385 times in the project

and as for other things, missionary is much simpler to use, because of the way errors are propagated

clojurescript in general is not particularly buildsize friendly

especially lazy-seq, have to be careful to use transducers or reducers like mapv instead o map