TimerErTim

I can't replicate this on the current master branch. Maybe it already has been fixed? @GabrielOlvH If this issue is still relevant, I would like to work on this.

I have already conceptualized another API proposal. It addresses some of the problems you mentioned. I will go into further detail further down below. I'd argue that `Shader` is the...

As I just got assigned a new project in school while barely having much free time at all I don't expect to be capable of working on this in the...

No problem! Thanks for merging

As a sidenote: The proposed solution would not only fix this concrete problem, but would also allow multiple, concurrent transactions, which would be a very nice feature to have.

Since this query: ```sql SELECT "something" FROM obj ``` also procudes a response similar to this: `["something": "something"]` I would declare this whole issue as intended behavior with missing documentation....

What is the current status regarding this issue? The problem still persists with Compose version 1.0.1 and freetype2 2.11.1-1. This is a major deal breaker as this also prevents any...

I opened this issue as I thought there occurred more compatibility issues with tetra 0.7.0 compared to pre releases. On my local environment it seemed your (@devmeat ) PR introduced...

I am not that familiar with RNNs but is it really necessary to manually provide the hidden state and return the new one as output? Wouldn't it just work if...

I may be wrong but I think neither PyTorch nor Tensorflow **requires** a hidden state as layer input. You can optionally provide it nonetheless to tell the layer what its...