m1cm1c

@SebastienGllmt I've had the same problem as you. I want to accept a body of type `Record` where `type UUID = string`. @yannbriancon's `{ [key: string]: unknown }` trick works...

For anyone interested: I wrote this function to achieve a similar effect: ``` (defun avy-goto-word-1-or-goto-line () (interactive) (setq headChar (read-char "char: " t)) (if (eq headChar 13) (progn (avy-goto-line) (move-end-of-line...

I propose a simple way of circumventing this issue in #2981.

@fvictorio This is exactly what my proposed fix boils down to, except it has the advantage that if true nested fixture support were to ever be implemented (i.e. not executing...

@dark64 Yes, it makes sense for compilation to fail. However, in my recent call with @Schaeff, he said that you guys are trying to get rid of compiler crashes and...

Interestingly, static analysis handles the write case: ```zokrates def main(): u32[16] memory = [0; 16] u32 f = memory[17] return ``` ``` $ zz compile -i bug.zok Compiling bug.zok Compilation...

> I'm not talking about the identifier nodes of variables of the enum's type. These are set correctly. They are. But I just noticed that they are set in a...

Is there any way to use an actual `Date` object in an entity when using Postgres? I cannot specify the type to be `datetime` because Postgres does not support this...

@Ginden I thought that I was using `timestamp` in all of my entities and that I wasn't getting `Date` objects regardless. However, I just discovered that I was using `time...

Has this a prospect of getting fixed? Has it already been fixed by someone, just not sent upstream?