oberblastmeister

Sliced interface for ShortByteString

9

I think we could take some inspiration from [byteslice](https://hackage.haskell.org/package/byteslice). This would also address https://github.com/haskell/bytestring/issues/193, by expanding the api for `ByteArray` based types instead of changing `ByteString` to use `ByteArray`. The...

Do not use `:` to separate linux devices

4

Interpreting `:` as separating devices is a bad idea. We should just allow a list to be passed to `linux-dev`. For example ``` (defcfg linux-dev (dev1 dev2 dev3) ) ```

Both modules don't expose much anyway and are mostly and implementation details.

Check for architectures that don't support unaligned reads?

4

I think there are some unaligned reads here, and some architectures don't support them.

In https://docs.rs/tree-sitter/latest/tree_sitter/struct.QueryCursor.html#method.matches the `text_provider` gets bound as ```rust T: TextProvider

The latest version fixes many bugs and offers a better api.

Should `Fn` have `{-# COMPLETE #-}`?

1

I keep getting warnings for incomplete patterns

Don't use streams and fusion

2

The documentation states > Starting from @text-1.3@ fusion is no longer implicit However, many functions still use `Stream` internally, even thought they would probably run a lot faster without it....

I'm thinking we should call it `Text.IO.Utf8`. I made a [pr](https://github.com/haskell/bytestring/pull/547) in bytestring which should be used for this.

Allow getting the buffer handle and make `Buffer` copy

2

Getting the internal handle is useful when `nxim_oxi` hasn't made bindings to something yet. I also don't see why `Buffer` shouldn't be `Copy`, as it's just an integer. I also...