Jakob Høgenes
Jakob Høgenes
I heard some rumors that we want to support multiple phone numbers for each data collector, correct? Then I assume that they will all have the same country code?
I like it, it is definitely annoying (and error prone) to make the mirror port every time we use ports. And sometimes I make two fragments with each of those...
Well that makes event less sense for me, why does it keep the value for C when State2 has no 'keeps history'?
Hmm, but then this doesn't seem so useful to me. So even though a composite that keeps history will re-enter into the last state, that last state will not keep...
By deep history you mean that all states keep their history, and by shallow history you mean?
So basically we just need an annotation, like `@checker_should_warn "true"`, which passes if: - There are no checker errors - There are 1 or more checker warnings Right?
Well, I have no strong opinions on the matter, but if we choose one, I guess we all agree that it should be the first option to keep. The grouping...
@brice-morin I don't think this is constrained to just functions, with regards to other properties that might not be initialised, you will have the same problem with e.g.: ``` thing...
I kind of forgot about arrays when I wrote the previous comment, which complicates things even further. IMO we should also re-think the static-size arrays in ThingML, it makes things...
I don't know if I am supposed to put complaints here, but I have issues with the first two: - `@sync_send`. In some languages, we cant do this, e.g. Go....