Inconveniences when using inner classes in Ivy Script

Question

Suppose I have two classes, each of them provides Builder API.

// This is in Ivy Script
import example.Person.Builder;

Builder errorPersonBuilder = new Person.Builder(); // this line generates a compilation error saying class Person.Builder not found.

Builder workingPersonBuilder = new Builder(); // this works.

It is still OK if there is only one Builder inside the context. As soon as there is another:

// This is in Ivy Script
import example.Person.Builder;
import example.Company.Builder; // compilation error of collision, there are two classes named Builder.


Builder workingPersonBuilder = new Builder(); // this works, see above.

Builder anotherBuilder = new Builder(); // which builder?

If Ivy Script could supports the same as normal Java, we could do:

import example.Person.Builder;
import example.Company.Builder;

Person.Builder personBuilder = new Person.Builder();
Company.Builder companyBuilder = new Company.Builder();

Should this be supported in Ivy Script?

Accepted Answer

Hi

This code here:

import example.Person.Builder;
import example.Company.Builder;

Person.Builder personBuilder = new Person.Builder();
Company.Builder companyBuilder = new Company.Builder();

does not work in Java as well. The compiler says:

The import test.Person.Builder collides with another import statement

In java and IvyScript the following works:

import test.Company;
import test.Person;

Person.Builder personBuilder = new Person.Builder();
Company.Builder companyBuilder = new Company.Builder();

If you are working with builders, we usally provide a static method to start building. E.g.:

public class Person
{
  public static Builder build()
  {
    return new Builder();
  }

  public static class Builder
  {}
}

Then you do not have to import the Builder itself. Simple use:

Person person = Person.build().withName("Weiss").withGender(Gender.MALE).toPerson();

Inconveniences when using inner classes in Ivy Script

Follow this question

Related questions