SPC-code

Results 15 issues of SPC-code

There are several cases in binary parsing, where one needs to wrap a `ByteArray` with an interface like `Source` and read from it sequentially. It should be possible by using...

enhancement
unsafe API

In protocol parsing/writing we frequently need to operate with one-byte encoded strings that a expected to consist only of ASCII characters. Please add an ability to convert a string literal...

encodings

It is important to be able to construct buffer-like object with builder. In the ktor-io it was `ByteReadPacked{}`. Here, I suggest this: ```kotlin fun Buffer(block: Sink.() -> Unit): Buffer ```...

enhancement
API improvement

Some APIs like `onChangeFunction` uses `org.w3c.dom.events.Event` while some APIs like `onTagEvent` uses `kotlinx.html.org.w3c.dom.events.Event`. It makes using both APIs in the same code hard.

It is required to create a common reading and writing rules. For example, TSV rule could look like this: ```kotlin val TSV: CsvContext.()->Unit = { charset = "ISO_8859_1" quoteChar =...

It will probably require exposing CsvFileWriter ability to write a single line.

Path is a more flexible alternative to a File. Aside from better API, it allows working with virtual file systems such as Jar/Zip/S3.

### Added - Reification. Explicit `SafeType` for algebras and buffers. - Integer division algebras. - Float32 geometries. - New Attributes-kt module that could be used as stand-alone. It declares. type-safe...

The idea is to implement serialization and direct zero-copy working with buffer-like structures using [Apache Arrow](https://arrow.apache.org/docs/index.html). Basically one needs to implement a `Buffer` and `MutableBuffer` on top of Arrow and...

good first issue
feature

After last additions, tensors contain a lot of non-idiomatic code and requires a lot of clean up. Overall architecture is more or less OK, but implementations are a mess.