`GapObj` vs `julia_to_gap`

[ThomasBreuer]

The use of GapObj as a constructor is getting more and more popular.
Currently the implementation provides just GapObj(obj, recursive), and GapObj(obj; recursive = false),
and delegates to the three argument version julia_to_gap(obj, IdDict(); recursive).

This way, calling GapObj with one argument often runs via julia_to_gap(obj, IdDict(); recursive) into the default method of julia_to_gap that discards the last two arguments.

Can't we use GapObj and julia_to_gap as synonyms?
Then this detour would be avoided, and the special one-argument method would be called directly.

[fingolfin]

How does this relate to issue #1025 which has basically the same title?

[ThomasBreuer]

Yes, I should have added the text from #1025 here, I simply did not remember that this issue existed already.

[fingolfin]

These days julia_to_gap and GapObj both delegate to GapObj_internal and so are essentially synonyms as suggested here, so I think we can close this now.