Can you instead add another example that explicitly describes how the struct-level option interacts with field level options. I think this can highlight the feature and caveats better.

I think compile_fail example perfect for that

This needs some related documentation or something. :)

Added documentation about struct level atrributes here

Functionally, it seems to make sense that this could work without erroring. If the field attributes take precedence can we implement them and not the struct level value, instead of erroring? It seems like a more flexible API.

If not, I think the compile_fail could be reduced to this:

    #[derive(Getters, Default)]
    #[get = "pub"]
    pub struct Foo {
        #[get] // Invalid!
        private: i32,
        public: i32,
    }

Then maybe we can have a full, valid example of the struct level attributes and field level working?

Sorry to be such a stickler about this. 🤣

It's compile_fail test not because we cannot mix struct and field level attributes. It's fine.
But generated getter is private, and we try to call it and this is compile time error.
I clarify this is with comment

Sorry to be such a stickler about this

It's fine