IIRC many websites (e.g. for buying concert tickets) have a lock mechanism where you have X amount of time to make your purchase during which time only a limited number of people can be in the checkout process.
I wonder what the prompt would look like as a sentence. Maybe activation maximization can be used to decipher it, maybe by seeing which sentence of length N would maximize similarity to the prompt when fed through a tokenizer
Well, you are not really seeing an eye in a mirror, you are just seeing a representation of it. The medium cannot depict all the dimensions and details of the object, so again you are able to see depictions, representations, and simplifications of it, but never truly be able to grasp the object itself.
Why not remove the ability to set a key to the null value then? Raise an error in the compiler. It seems pretty undesirable to have undefined behavior in the language, and if high performance is one of your goals, remove the ability for users to do the low performance things.
Seems like an interesting way of doing it. Why generate the argument configuration from the documentation rather than generating the documentation from the argument configuration? Where there some pain points you wanted to solve from `getopt`, etc.?
A river flows in one way rather than another because the particles that form the river have momentum one way rather than another. The reason they have this momentum is because the surfaces of the river interact with the air, obstacles, and the rock bed underneath it, and then pass on momentum to internal river particles, which pass on that momentum to other particles, etc. In this way, is the river not processing information regarding things it can directly "observe" about its environment at its surface, as well as the things it has experienced in the past, then processing that information deeper and deeper, until it ultimately leads to a decision on which way the river flows?
This is cool! I suggest adding some more hints to indicate how important/relevant different papers are. Maybe some tags to classify papers in different fields, and number of citations or amount of discussions online as a metric of how big a paper is? (I know that's not a great metric but I think it's still better than seeing a bunch of papers and not knowing which ones are worth reading). You can also spark discussions. Seeing "0 comments" discourages anyone to look at the comments, but even having an AI-generated summary as a comment can be encouraging and spark discussions. Just a thought.
Would you accept a PR for first-class support for specifying constraints between variables (and object measurements) as part of the language or would that be divergent with the goals of the language? I find it to be an important part of SolidWorks etc. because often times I'm trying to build something where I know one of the dimensions is constrained a certain way but that's not how I'd parameterize the object. And I don't want to be doing math for e.g. calculating the diagonal over and over again as part of calculating parameter values or modeling constraints, I like that in Solidworks that's part of the package. I believe this issue is important to other mechanical engineers as well.
However I do want to say, great work, I think a programming language is a great step forward for CAD regardless, and this project seems to be pretty well done!
This is great! I've been looking for something like this for a while. My only question is: does this do constraint-based modeling like other CAD software or do you have to specify individual parameter values?