Mesa Can Finally Build With Almost No Compiler Warnings

[varikonniemi]

>Soooo the code is correct so there's nothing to change. But how would you change the compiler so that it knows that a specific path can't be longer than 4096? Let me know if you find out

I don't know what is needed in newer gcc versions, last time i compiled C we were at version 6.

But putting a length assert might do it? Or what pal666 said.

[RealNC]

Slow Friday? :P

[moilami]

Have we playing with a snake today

Yes...

https://www.youtube.com/watch?time_continue=3&v=oiGRoEhjXgA

[cen1]

Quite an achievement. I think the "no warning" zealots are wrong tho, a lot of warnings are just pure bullshit which doesn't effect anything.

[caligula]

Quite an achievement. I think the "no warning" zealots are wrong tho, a lot of warnings are just pure bullshit which doesn't effect anything.

There's a systemic problem if there's an impedance mismatch between warnings and pro developer intentions. One example is switch-case. In C/C++/Java you can't guarantee that all cases break and the values are not uninitialized in some cases. The solution would be to use functional pattern matching and total patterns.

[fuzz]

It's not very motivating to fix mysterious issues caused by careless mediocre coders when they can have all the fun focusing on shiny new features.

Normally I would agree, however most of these people are getting paid by companies to implement new features. Huge, huge difference. I certainly don't get to choose what I spend my time on when I code for work.

[fuzz]

pass size, so compiler could ensure that code is correct.

Maybe it would be better to use a language that implements memory ownership as a feature.

[caligula]

Normally I would agree, however most of these people are getting paid by companies to implement new features. Huge, huge difference. I certainly don't get to choose what I spend my time on when I code for work.

Anyway, fixing other people's bugs is something many don't wish to do. Probably explains why it's so tempting to just fork or reimplement from scratch than to fix broken existing systems.

[brrrrttttt]

Then fix it before your next release. Either in your code, or in the official compiler you use. GCC gives warnings when it should not? Use clang.

This really just betrays your inexperience, especially the last part.

[pal666]

Maybe it would be better to use a language that implements memory ownership as a feature.

mesa already uses c++ in some places. well, c++ by file type, not necessarily by contents