Adrian Sampson
Adrian Sampson
Wonderful; thank you for summarizing this so clearly! Indeed, both of these would be great advances that would "modernize" our hardware generation. One small operational note: the eDSL adoption can...
Indeed. Sticking with `.gfa` files is the right thing to do here because (a) they are the "source of truth," (b) odgi is a difficult-to-install dependency (to put it lightly),...
I think this is another "YAGNI" situation: let's parse these if (and only if) we know of a specific odgi command that needs to know about them. @susan-garry, did you...
Awesome; thanks for getting this conversation started! I think the first thing to do here is to build a round-trip converter between GFA and _some_ binary format. This binary format...
Yay; this would be very satisfying!!
Great; thanks! One minor question: > * Initializing variables without a type annotation (i.e., `my_bool: bool = false;` parses, but `my_bool = false;` fails) > * Parsing a new Strand:...
This would be fun to brainstorm about in more detail. One thing I'd be particularly interested in considering is what should be Filament-specific vs. what should be more general and...
Drive-by comment that may be entirely obvious: in an extremely high-level way, this resembles method overloading in OO languages. That is, in overloading, the behavior (and the return type) depends...
Cool; this sounds like the essence of the matter: > Each event is explicitly tied to a particular clock domain and events from different domains are not allowed to reuse...