Some of the issues below are already mentioned in other tickets, but I have the feeling that a proper generic issue is due to give it visibility, as for now the current package is unusable for many users.

1. The typescript package doesn't respect the tsconfig flags, and many of them are hardcoded inside the meteor/babel package.
   I understand that meteor needs to control some compilation option

MobX 6

Hi folks, I've tinkered a lot about MobX 6 lately, so I want to layout the vision I have currently

Goals

🧨 1. Become compatible with modern ES standards

Let's start with the elephant in the room.
I think we have to drop the support for decorators.
Some have been advocating this for years, others totally love decorators.
Personally I hate to let decorators go. I think

When I open any chapter, say ch01:
https://mostly-adequate.gitbooks.io/mostly-adequate-guide/content/ch01.html

Right chevron links to the current chapter header. I'd expect it to link to the next one.

Env:

MacOS
Desktop Chrome v79 (latest)

I haven't used Gitbook, but it might be solvable via GitBook update, also mentioned in #542

As explained at CycleConf I will work (hopefully with the help of others) on the docs. It will be more a very long tutorial, like a book, starting simple, ending at #705

Planned chapters:

• Getting started (setting up a project)
• Streams
• First component
  • Rendering static content
  • Handling events
  • Having local state
  • Making our input controlled

Describe the bug

Recently C

@mweststrate With 6.0 out now (👏), would you consider trimming down README and consolidate that at the docs site I've made? I still haven't got any feedback about that site from you.

https://mobx-react.js.org

Red/System []
s2: declare struct! [
   a   [integer!]
   b   [c-string!]
   c   [struct! [d [integer!] e [float!]] value]
]
probe size? s2

Taken from https://static.red-lang.org/red-system-specs.html#section-4.7.2
Says:

Compiling to native code...
*** Red/System Compiler Internal Error: Script Error : last expected series argument of type: series port tuple
*** Where: for

The logged output does not match the example above.
For each i value, we should see something like i: 0 instead of just 0 for example.

Hi! Thanks again for creating ReactiveSwift! I've searched around a bit online and can't find what I'm looking for.

The APIContracts used to include this best p

The documentation explains pretty well why:

Wrap ALL of your components with view - including class and function ones - even if they don't seem to directly use a store.

I think it's pretty easy to miss adding this view hoc when you write hundred of components. My question is: Is there an eslint rule which exists to warn you that you forgot to add this extra view?

It could be nice to

I think the documentation must include a note on the diamond flow and how xstream manage it, something like an explanation of atomic updates of flyd.

As well described by @staltz in this answer would be best to avoid diamond shaped stream graph:

![ima

The methods in ProtectedData.cs are very misleading.

Instead of returning the original data they should throw an exception explaining that they are shims and not intended to be used as-is without overriding.

Some of the benchmarks don't have the correct scala doc, fixing those.

• https://github.com/monix/monix/blob/master/benchmarks/vnext/src/main/scala/monix/benchmarks/AsyncQueueBenchmark.scala#L41
• https://github.com/monix/monix/blob/master/benchmarks/shared/src/main/scala/monix/benchmarks/CoevalAttemptBenchmark.scala#L38
• https://github.com/monix/monix/blob/master/benchmarks/shared/src/main/

When I click "live" on any of the links under https://router5.js.org/#examples

I see that router5 version is still 6, the redux example in particular still uses react-redux 5(current is 7)

If you present a UIViewController and from that screen you make a step which change flow will create a memory leak by holding the NavigationController with full stack of ViewController within it. That flow is deallocated but the navigation controller and other view controller still exists on memory.

Global roadmap can be found here: https://trello.com/b/1q0TNsWv/neutronium
Note that this roadmap is susceptible to changes.

Version 1.7.0

• Neutronium.Core
  • Support of binding to IObservable interface

Version 1.8.0

• Neutronium.Core
  • Support of complex javascript deserialization when used as command argument (Today only basic types and object converted from C# are supp

Linq added some awareness of bypass operations for standard operations to speed things up.

They achieve this with the IPartition and the IListProvider interfaces

https://github.com/dotnet/corefx/blob/master/src/System.Linq/src/System/Linq/IPartition.cs
https://github.com/dotnet/corefx/blob/master/src/System.Linq/src/System/Linq/IIListProvider.cs

Eg if someone uses Linq Count() method, if