E07175: default constructor must be 'private' when uninitialised properties exist
What went wrong
A class has uninitialised properties and developer-coded constructors, but the default (no-argument) constructor is still public. This allows callers to bypass the developer constructors and create objects with uninitialised properties.
Worked examples
Compilable examples demonstrating this error and the correct fix:
- ek9 -q 886 (Why must a default constructor be private when a class ha...)
How to fix it
- Add 'default private ClassName()' to make the default constructor private
- Or initialise all properties at declaration (e.g., name <- "")
- The goal is to ensure every externally callable constructor initialises all properties
Common causes
- Added a constructor for initialisation but forgot to restrict the default constructor
- Assumed that adding a developer constructor would suppress the default one (it does not in EK9)
- A 'default' no-arg constructor on a dynamic class that captures values: it receives none of them
See also
Examples
Every example is compiled by the EK9 compiler: the first fails exactly as captioned, the others fix it.
Fails with E07175: default constructor must be 'private' when uninitialised properties exist
#!ek9 defines module error.e07175.bad defines class //owner is unset until a constructor sets it, yet a public no-argument constructor is generated Account owner as String? Account() -> name as String this.owner: name describe() as pure <- rtn as String: `Owned by ${owner}` default operator ?
Fixed: Make the no-argument constructor private
#!ek9 defines module error.e07175.good defines class Account owner as String? //Only the class itself can make an Account with no owner default private Account() Account() -> name as String this.owner: name describe() as pure <- rtn as String: `Owned by ${owner}` default operator ?
Questions and answers
These Q&A entries show E07175 and its fix:
Found a problem?
If EK9 reported E07175 for a program you think is valid, or did not report it where it should have, use the compiler form with the smallest program that shows it. If this page is wrong or unclear, use the documentation form. Both are at github.com/ek9lang/ek9-issues.