I gather from your explanation, that in order to tell before hand whether or not a type will be inferred, you really need to examine the code and see how things are being handled, and optimized out. (And even then you still may not know) Interesting, thanks.

Got it, this completely made sense after your explanation and a second look. Also before I saw this example I hadn't thought about being able to pass arrays and tuples as generic parameters types. Thanks

wtf, lol that must be some damn good butta!

and very soon Facebook as well...

Ah, good point. I do have a monitor with HDR, but I never really paid attention to it in the past. AFAIK unfortunately there isn't really any good support for HDR without a lot of messing with the window server. It seems to be in the works though by various groups.

Video of the tech: https://www.youtube.com/watch?v=UI-t21QcXM4

Jumped back into Octopath traveler. After a bit of a hiatus.

Wheres my cut?

Agreed, this experiment should be able to last by itself without feeling obligated to post something. If that's the case then it's failed.

If the code is written well, it can save a bunch of time and provide a great forum for learning new techniques. Otherwise, if it's written poorly yes I hate it. Like others have state here the title is an over generalization.

This is really useful info, can you recommend a tutorial that you feel shows how to effectively use these tools along with traditional style coding? Or would you say it's just a try and see approach/learn as you go. Personally, I think your comment best demonstrates where we are right now with AI assisted development.