rdescartes

If it’s possible, that would be awesome. Do you mean that the author of the proc macro provides that information through attributes?

(Disclosure: I originally implemented the proc-macro part of RA.)

Could you mind to tell me what is your plan on proc-macros ? You said you have an idea to “will not require actual code execution”. On the other hand, RA current method of handling in Proc-Macros are very fragile.

Should it be named Shanghai solitaire Or Mahjong Solitaire ?

Why firefox in andriod is "more vulnerable to exploitation" ?

From that paper:

    There exists a class of questions in life that appear remarkably simple in structure and yet contain infinite complexity in their resolution space. Consider the familiar or even archetypal inquiry: "Darling, please be honest: have I gained weight?"

If you want to get a good result, the grammar should be following the expect output from the prompt, especially if you use a small model. Normally I would manually fine-tune the prompt to output the grammar format first, and then apply the grammar in production.

I apologize for going off topic, but may I kindly ask how one might go about learning these things?

> Another reason I love Rust. It’s very statically analyzable.

Proc-macro in Rust is very tricky to analyze statically, some are even impossible (due to non-deterministic behavior)

Functional constituencies are part of the Hong Kong legislature. Imagine that half of the US Congress is appointed by the President of the United States.

Does anyone know how Fall Guy's net code was implemented? It's very smooth with 100 participants.

unsafe { comp.lang.c }

One of my friends used the same strategy to block DDOS from China : just put "Falun Gong" on there and it was resolved instantly.