Daniel Klauer

The crash happens with plain C too: https://gitlab.gnome.org/GNOME/gtk/-/issues/3310

It could be because of string indexing; there were quite some special cases in fbc treating z/wstring pointer deref's specially because of that, treating such expressions as wchar/char integers in...

I don't know what advantage there is to allowing this (static i.e. non-member operator overloads inside UDT/class) particularly for operators, but maybe it's about the same as for static member...

For the last Windows API binding update I've generated ntdef.bi using fbfrog ([here](https://github.com/dkl/fbbindings/blob/7ff38d74880d9d637b5f70679d72e4614a3abb7b/makefile#L2925)), not tested though.

Yea, looks like this issue with "make bootstrap" was overlooked. Normally (from my point of view) fbc is built using an existing fbc, which itself checks for libtinfo when linking...

Some related information: This sounds to me like it's the classic `redim` parsing issue. Since it can be used to declare variables, there needed to be some differentiation between `redim...

Sounds like it's probably the same as #691.

Hi, I'd like to help out with finishing this. @rrichardson, did you still plan to work on it, or is it ok if I rebase and re-submit the pull request?...

Hey again, I tried writing an RFC for it (since it's an addition to std): https://github.com/dkl/rust-rfcs/blob/unixsocket-seqpacket/text/0000-unix-socket-seqpacket.md Does that seem reasonable? Any suggestions before submitting?

Looks like the typedef cast is what breaks it, this seems to work: ``` #define jit_label_undefined2 ((size_t)~((unsigned int)0)) ``` ``` const jit_label_undefined2 = cuint(culng(not culng(0))) ```