Thank you for the feedback! I agree it does obfuscate the signature, possibly too much. I think it's okay as long as the user has the option to do both, with this made clear in the docs.

Also, yes I agree, RequestContext makes more sense!

Hi, I have been coding on GitHub for about 2 years. There's no trick other than enjoying it and relentlessly programming for fun. You probably know this, but if you enjoy something, you'll likely be better at it than someone who doesn't! More concrete advice would be to become an expert on the fundamentals and then try to tackle large projects, things that you think you could definitely not do, but do them anyway.

I appreciate the response! Was there any structured curriculum you used for learning the fundamentals? As someone who isn’t in a CS program, I was wondering where a good place to start would be

No problem! With C, I started with the K&R book. This provided a great foundation for C and some fundamental CS concepts. I am unsure of the best way to obtain a more structured curriculum outside of college, as that is how I received mine. There are many YouTube video courses to choose from if that is the type of content you learn best from. And many for CS fundamentals. I would also highly recommend a combination of project-based learning with theory, as that will accelerate your understanding quite a bit. You could try looking for a programming buddy on Reddit on r/programming, too! Having someone at a similar skill level to you will make learning easier as you both share knowledge.

That's a very good idea actually and I had wanted to do that but it didn't click that you could do that with a macro!

Thank you, I'll will implement that :)

For the ultimate in readable test reports, you can prettify the test name by:

* dropping the prefix "test_" * substituting the "_" characters in the function for whitespace * uppercasing the first letter of each word.

So `test_tokenize_simple_model` becomes "Tokenize Simple Model".

Thank you, I really appreciate you saying that!

Yes it's on the backlog and will be fun to implement :)

Thank you for the feedback, it is appreciated!

I did intend to implement parallelization as a later feature so it's good to bring it up.

Yes, I'm sure that is something I can add to it.

I will add it to the backlog of things to do :)

Haha, the example could be better. All of the other things combined, I would say it could be called a framework.

There are some more examples in doc/

Thank you, that means a lot! :)

Wow! That really means a lot because I always make a lot of effort to make sure my code is just that :)

Appreciate you saying that!

You've done a couple of things right: very few dependencies, simple, easy to understand code. C gets hairy when you try to be clever.

I'm busy writing some of the most optimized-but-still-portable code that I've ever written and it is very interesting to see how even a slight difference in how you express something can cause a massive difference in execution speed (especially, obviously, in inner loops). Your code is clearly written from what your comfort zone with C is and I'm really impressed by the restraint on display. At the same time, some of the code feels a bit repetitive and would benefit from more universal mechanisms. But that would require more effort and I'm not even sure if that is productive. One part where I see this is in the argument parsing code as well as in the way you handle strings, it is all coded very explicitly, which substantially increases the chance of making a mistake.

Another limitation is that using AI to help you write the code means you don't actually understand what it does, and this in turn may expose you to side effects that you are not able to eliminate because you did not consider them while writing, it is as if someone else gave you that code and asked you to trust them they did not make any mistakes.

Thank you so much! I appreciate it :) And yes, totally agree.