muelli
muelli
@Cropi do you have any opinion on the integer overflow?
ah, sounds like a valid approach. More sane, anyway, than a device obtaining the reserved LastID. I wouldn't know how to test for the availability of an ID. I also...
I've rebased the patch.
`pip install --upgrade 'pulp
seems nobody has suggested to use the [Seahorse API](https://gitlab.gnome.org/GNOME/seahorse/-/blob/SEAHORSE_0_9_10/tests/dbus-crypto-test.py) just yet, but it may be worth a shot.
FTR: @tunguski has a fork here: https://github.com/tunguski/elm-ast that seems work well with comments. At least the example page https://tunguski.github.io/elm-ast/example/ parses the code from https://github.com/Bogdanp/elm-ast/issues/41#issue-229655914 https://github.com/tunguski/elm-ast/issues/3 refers to https://github.com/tunguski/elm-ast/commit/60a771c2ae3e3fac5185b2bbfb2e14e3af72d2bf
I'm throwing in a wild idea: How about some manual pre-processing of the modules? In particular, stripping `--` comments to alleviate the problems experienced in #15. Also note https://github.com/andre-dietrich/parser-combinators
> You mention making the `.d.ts` files more comprehensible. But that doesn't seem necessary to me, it's just an internal detail that's hidden from the user, right? Yes and no....
Cool. This makes types for the argument to `subscribe` and `send`, right? It is possible to further split the types up? I.e. to have a type for `name` or `ingredient`?
The answer is: yes. ``` type Ingredient = RecipeIn['ingredients'][0] ``` This is very amazing. Thanks for pointing these types out.