Giter Club home page Giter Club logo

reactive's People

Contributors

tower120 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

reactive's Issues

DeferredForwardContainer::void foreach(Closure&& closure) conflicts with Qt foreach

It's not a fault of the library, but it'd be great if you could rename foreach to for_each or smth like that. The problem is that Qt has macro foreach and it conflicts with your function

template
void foreach(Closure&& closure) {

as result there are errors in msvc and qt:

master\src\reactive\details\utils\deferredforwardcontainer.h(118): warning C4003: not enough arguments for function-like macro invocation 'Q_FOREACH' (compiling source file QtBindings.cpp)
master\src\reactive\details\utils\deferredforwardcontainer.h(118): error C2988: unrecognizable template declaration/definition (compiling source file QtBindings.cpp)
master\src\reactive\details\utils\deferredforwardcontainer.h(126): note: see reference to class template instantiation 'utils::DeferredForwardContainer<T,DeferredActionValue,ActionListLock,ListMutationLock,unordered>' being compiled (compiling source file QtBindings.cpp)

writing #undef foreach is very annoying before reactive's includes

Documentation is outdated, and nothing compiles

#include <reactive/ObservableProperty>

is no longer valid. Now it's

#include <reactive/ObservableProperty.h>
  1. Just one line
#include <reactive/ObservableProperty.h>

already breaks the build process.

This is yet another so-called 'reactive' library I found, and none simply 'works'. What a shame.

What is the best way to capture ObservableProperty?

Sorry, I have not found your email, but I'm wondering what is the best way to capture ObservableProperty in lambda? is it better to use by ref, by value or shared_ptr? another question - what is the best way to pass ObservableProperty to function - by ref, by value or shared_ptr?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.