Can flyd streams be made lazy ? about flyd

[nordfjord]

you could maybe do something like:

const start = flyd.stream();
const readFile = (file)=> {
  const s = flyd.stream();
  fs.readFile(file, s);
}
const read_hello = start.chain(()=> readFile('./hello.txt'));

read_hello.map(fileContents => console.log(fileContents));

start(true);

[nordfjord]

Hey @sourcevault ! Glad you found a solution!

I think you might be able to make a generic nodeback -> Stream function.

function fromNode(fn) {
  return (...args)=> {
    const s = stream()
    fn(...args, (err, data)=> s(data))
    return s
  }
}

Then you could use that as:

const readFile = fromNode(fs.readFile)

readFile('file1.txt')
  .map(x => x.toString())
  .map(console.log)

[nordfjord]

don't worry, I understand what you're trying to accomplish.

I'm curious about your use case though, what use case do you have that requires lazy streams?

[StreetStrider]

Afaik, flyd is push by it's nature.
Check for pull-stream, Highland.js (they're oriented to pull strategy) and most.js (starting cold).

[sourcevault]

@StreetStrider it should be possible to express a push stream as a pull stream given that their operations are similar. I do not know what the theoretical equivalence law is.

@nordfjord yep - that seems like a cool workaround :D using chains !

Thank you both !

[sourcevault]

Hi @nordfjord !

const read_hello = start.chain(()=> readFile('./hello.txt'));

readFile would return undefined not a flyd stream.

I can think of creating a wrapper and create .run method but there might be a clever trick.

[sourcevault]

  var flyd = require('flyd')

  var fs = require('fs')

  readfile = function(name){

    var s = flyd.stream()

    var F = fs.readFile(name, function(err, data){return s(data.toString())})

    setTimeout(F, 0);

    return s;
  };

  stream = readfile('file1.txt');

  stream.map(function(data){

    console.log(data);

  });

Using setTimeout as a hack.

[sourcevault]

Hallo @nordfjord !! 😀

const readFile = fromNode(fs.readFile)

readFile('file1.txt') // <-- 1) This still runs immediately 
  .map(x => x.toString()) // <-- 2) This runs after [1]
  .map(console.log)

I don't think there is a way without using setTimeout to delay [1].

@nordfjord are you familiar with mostjs ?

https://github.com/cujojs/most

It runs / delays all side effects till all the .maps etc are defined, its said to be lazy.

flyd is more 'active', but I am trying to find a way to make it lazy, I hope I am making some sense.

[sourcevault]

It is more of a intellectual curiosity when you corner me like that @nordfjord ☺️.

I have no immediate usecase, most streams work fine on node events like fs.readFile.

But then things like fs.watch flyd is a better choice.

I was hoping if there was a way to make flyd work for all most.js usecases.

I have looked at some libuv internals and using setTimeout 0 with flyd should be fine.

libuv runs everything with setTimeout 0 in the next tick, making it lazy so to speak.