nopeslide

Results 27 issues of nopeslide

Instead of using onnx structs directly I would like to wrap them in a simple manner like: ```c typedef struct { Onnx__TensorProto onnx; } tensor; ``` So if we need...

without weak attributes we need to rethink how to make the info structure optional. I see following options: 1. duplicate the set structure, one for the resolvers, one for the...

added fields to return value of get_files - "fileset": fileset which included the src file - "core": name of the core which included the src file - "depend": name list...

when using `__VA_OPT__` you can make this even more compact ``` #define EVAL0(...) __VA_ARGS__ #define EVAL1(...) EVAL0( EVAL0 ( EVAL0 ( __VA_ARGS__ ))) #define EVAL2(...) EVAL1( EVAL1 ( EVAL1 (...

Instead of having a handy way to quickly instantiate the various protocols in common as standalone bytefield, lets make them fields, that can be used in other bytefields. these fields...

enhancement
help wanted
good first issue

Small usage improvement. Every field represents some text at the end and afaik fields do not use length or color arguments. instead of ```typst bytes(3)[ #box(width:100%,height:100%,fill:green)[ #text(8pt)[ my bytes ]...

feature-request

Introduce a new field that simply draws a gap of the specified height between two rows and a centered text. I.e. `gap(1cm)[]` or `gap[]` for some small default length (maybe...

enhancement