Closed zigster64 closed 1 month ago
I don't mind making stuff public :)
Tabs are objectively more accessible. It allows the width to be set by the user, independently of the font-size, which is important for those with poor eyesight. Supposedly, it's much better for users that use braille display. But don't bring it up with Andrew cuz he really hates this topic and feels very strongly that the issue here are editors and that this should be solved by editors.
I used zig fmt in httpz because it was more popular with more contributors.
See my branch - export_iterator for 3 changes
I wont put up a PR, because its a tiny change, and formatting differences are huge (8 space tab stops on your code ?)
Situation :
I want to create a simple wrapper struct over an SQL statement that gets re-used in many spots. Do not want consumers of the SQL statement to have to fiddle with setting index values, or copypasting custom logic on a per row level.
This is easy enough to do ... until you hit a statement that includes an iterator result type. (because you need an instance of the row do be able to get an iterator ... so you cant easily define a receiver struct that includes an iterator field without have a row)
eg:
Consumer use case
There might be a simple way of doing the same thing without exporting pg.Iterator, but I cant see it yet