Many or few constructor signatures?

[Tamas_Papp]

This may not be new (since you participated in the topic), but

Recommended style for conversion vs. constructors in v0.7

I’ve been upgrading a few packages to v0.7, and one of the biggest sources of deprecations is the removal of the default constructor->convert fallback. For those unfamiliar, previously if you had: struct T ... end Base.convert(::Type{T}, x::Int) = (construct a new T from an Int) then you you could call T(1) and, if there was not constructor matching (::Int), then convert(T, 1) would automatically be called for you. That was convenient but also kind of muddied the distinction between convers…

has a lot of good advice for constructors.

I would not worry about too many outer constructor methods per se, eg DataFrames.DataFrame has 16 outer methods (and 1 inner constructor).

However, if you need more than a few (ideally 1) inner constructors (eg for validation), you may be doing something wrong.