I havent mentioned anything about getting an error. I am not even using the ugradable plugins for deploying. I am simply asking why initializing an immutable in the implementation constructor is not supported with open zeppelin tools since it has nothing to do with the storage hence has no effect on proxy & implementation storage segregation.
Let me rephrase: Implementation shouldnt have constructors because they have no effect on the proxy storage. That is fine and makes sense. On the other hand, immutables are not stored on storage and are a part of the implementation which is totally fine. So why not allow immutables on implementation constructor ?
An answer would be: Well, its more work for the plug in to differentiate between constructors with only immutable initialization (which is fine) and constructors with actual storage initialization (which is not fine) so plug in basically forbids all implementation constructors. I would be happy with this answer but i would rather have it confirmed