the other part of this thinking about stories is to recognize that we don't know the worlds around us the systems 01:14:16 around us well enough to know that good things are impossible

therefore in practice it's a bit academic to worry about which lines inside that block the compiler should be happy or unhappy about. From falsehood, anythihng follows. So the compiler is free to say "if the impossible happens, then X is an error" or "if the impossible happens, then X is not an error". Both are valid (although one might be more or less surprising to developers).

This is a copy of the "AMD" document in the repo, kept here to maintain historical links. If this document differs from the one in the repo, the repo version is the correct one.

In other words, once you've used Maybe you cannot hit nil with a missing method. This is remarkable because even &. doesn't save you from omitting || "No state" at the end of the computation. Basically, that's what they call "Type Safety".

I guess it's about "preloading" and not "navigation", if it's the case, then I guess there is still no way to attach to navigation events, and this issue should be kept open.

No JS event is fired, so there currently isn't any clean way to do this that I can see.

Sometimes, when people are asked their preferences through a series of binary questions, they will give logically impossible responses: 1 is better than 2, and 2 is better than 3, but 3 is better than 1.

I also tried to use <!-- svelte-ignore unused-export-let --> before the script tag but still no chance.

You can't, currently. There is an open issue for this #4652

Looking at all those bearing, heading, orientation, navigation, position, direction, etc. I think we have a bigger problem here. Someone has decided how to use tag (e.g. orientation is about page orientation), but there are 100 other cases. Imho, to disallow misusing there should be no "heading", but rather "html-heading", "gps-heading", "whatelse-heading", which make mistakes impossible. So yes, "heading" should go.

This does solve the problem, but now our project and API is structured differently. In large projects it might be very hard to determine how to pull this trick off, or even impossible!

We aim to support all svelte features. In some cases this is not possible. For those cases we provided feasible workarounds.

There is a killer feature of vDOM that Svelte has nothing to replace with. It is the ability to treat component hierarchy as an object.

This is a very simple task for React and literally impossible for Svelte.

This is an ES5-only and un-shimmable feature, which is why Vue doesn’t support IE8 and below.

I am looking for indirect access via some sort of settings or confirmation, or proof that it is impossible.

Due to that, you have 100% data ownership as Matomo is hosted on your own servers and we have absolutely no way of gaining access to your data.

when you choose Matomo Cloud, we acknowledge in our Terms that you own all rights, titles, and interest to your users’ data. We obtain no rights from you to your users data. This means we can’t on-sell it to third parties, we can’t claim ownership of it, you can export your data anytime

MobX makes state management simple again by addressing the root issue: it makes it impossible to produce an inconsistent state.

The four general lines of argument are: (1) The Possible and Impossible; (2) Fact Past; (3) Fact Future; (4) Degree.