Open Feliix42 opened 5 years ago
I think so. The way I wrote it was that basically anything the user imports via explicit import declarations end up as sf dependencies and not the internal stuff, with the reasoning being that these should exist anyway.
However if you wold prefer we add them to the dependencies list that could certainly be done.
But then, smap
itself should not be listed as sf dependency, as @sertel pointed out correctly.
The rust implementation uses the operators itself and resolves ohua/lang
dependencies internally.
Oh ... heh :sweat_smile:
I just discovered that when writing a Rust-esque ohua file that involves a smap function (like this one), the compiled output will not list the
ohua/lang
functionssize
,oneToN
,smapFun
andcollect
as sf dependencies. Is this intended behavior?The compiled output for the above file can be found here.