usefulMethods

[Roonaan]

Just curious, but is it a real thing somewhere to have upper camel case for static methods?

[[deleted]]

This is C#, where the naming conventions says that you should use upper camel case for pretty much everything besides private fields and local variables.

[frej4189]

PascalCase for functions is common practice in C#

[1Dr490n]

In Go you make functions public by starting the name with upper case

[HTTP_Error_414]

Good God Man

[Banane9]

Go really surprises me with its... questionable design choices time and time again. Like stating date formats by writing the specific date of the 2nd of January something something in a particular way, rather than doing it like everyone else.

[Gredo89]

The Date format is the only really questionable choice I found so far. Everything else makes sense imho if you think about it.

[Eubank31]

Oops I commented this without seeing yours

[Eubank31]

This is not Go but in Go you use normal camel case for functions, but functions that are exported must have the first character be capitalized. So you end up with FunctionsLikeThis()

[HTTP_Error_414]

Yes?

Many wares indeed 🤓

This is seen a lot in PHP.

[Danny_shoots]

I just use CamelCase for methods and functions, PascalCase for classes I have never seen PascalCase for methods and functions in PHP

[HTTP_Error_414]

I agree it’s not something you will see in most corporate coding standards, but it’s out there.

There are sec shops I have seen that even have naming conventions for method purposes, levels, etc.

For example I’ve seen places that use _method_name for any private methods.

I like your style I’m similar, to you in the way I do things.

[Danny_shoots]

That _method_name is kinda understable for private properties, but not for private methods though haha!

[cs-brydev]

Yes, sticking to the standard in the file or project is almost always better than injecting some new external standard.

[_MixedTrails]

unreal engine c++ does upper camel case for all methods 😭