Error reporting suggestions

[jimc]

We have an app that scans MP3 files on your hard drive.

I’m getting a lot of these:

        if (bitrateIndex == 0)
        {
            jassertfalse; // This means the file is using "free format". Apparently very few decoders
                          // support this mode, and this one certainly doesn't handle it correctly!
            frameSize = 0;
            return ParseSuccessful::no;
        }

[...]

            if (successful == MP3Frame::ParseSuccessful::no)
                return -1;

Which is fine - so it’s an unsupported format.

But (as is common with many JUCE functions) the error reporting is a bit shite.

You just get a false from AudioFormatReader.

It would be a major improvement if ALL juce functions could return somehow detailed error messages which we could use to explain to the user what is going wrong (see also most of the File:: functions and the URL functions!).

It would be useful if everything in JUCE reported proper error messages, and included any OS error code information.

[AdamVenn]

Just voted!

[FR] juce::Expected

Similar to how we had juce::Optional as a placeholder for std::optional before moving to C++17, it’d be great to get a juce::Expected as a placeholder for std::expected before moving to C++23. std::expected works very similarly to std::optional in that it either will or won’t hold a value of the specified type. The advantage of std::expected over std::optional however is that you can also specify an error type for when there’s no value to explain why there’s no value. // Must use exceptions or…

Er, don’t scroll down.