Bob Weinand
Bob Weinand
If your Observable doesn't implement Promise, sure. And thus this is not on-topic on this spec.
@trowski Yeah, I realized I was confusing some people with this by assuming the Amp Observables; sorry for that. Also, yes, it would never resolve, but I TBH consider that...
Our amp observables (as in current master) allow subscribing with a callback which will be updated each time a new value is emitted. The end of emitting will be signaled...
This specific parser error happens when `typedef` is followed by a not defined identifier. On my linux system `/usr/include/x86_64-linux-gnu/bits/types.h` defines __int_least8_t (which is included from `` on my system). Does...
Sorry for the delay, yes, I can reproduce it and am looking into it.
The problem is that these macros are gcc predefined macros, concretely it does not find `__INT_LEAST8_TYPE__` here. If you check `echo | gcc -E -xc -v -dM -` you'll find...
Ah, I see, you have 1.0.0, which gets interpreted as number :-D (I had 1.0.3-dev which was not recognized as number) Fixed.
I will check it out (yes, I can reproduce it), but given it's only warning, I wasn't looking at it with high priority.
@cayolblake I'm working on it - it needs recursively resolving all referenced shared libraries for all supported targets (ELF and MachO), which is a tiny bit bigger feature, please be...
@cayolblake I've just added recursive symbol resolution for shared objects. There should be a lot less warnings now.