[m-dev.] hl (not hlc) grades

Zoltan Somogyi zoltan.somogyi at runbox.com
Sun Apr 5 20:12:36 AEST 2020

On Sun, 5 Apr 2020 14:12:41 +1000 (AEST), Julien Fischer <jfischer at opturion.com> wrote:
> > Do we support the hl.gc grade (which uses high level data
> > as well as high level code), or don't we? I seem to recall
> > that we discussed removing support for the hl grade component,
> > as we did with hlc_nest and hl_nest, but I don't recall the
> > result, and I can't find the relevant discussion in mrev or mdev.
> We certainly removed (some of) the user facing documentation for it.
> (I just noticed a couple of references leftover in the user guide.)

By "for it", do you mean the nest grade component, or the hl component?

> I don't recall ever reaching a decision as to whether the hl.* grades
> should be dropped. 

I don't either, hence my question.

> In the past there has been some small value in their
> presence; having a C grade that used --high-level-data was useful for
> developing other backends that use that option (e.g. Java and C#).
> If the last lot of benchmarking results I did between hlc.gc and hl.gc
> (which was a *very* long time ago) hold, then there's no compelling
> reason to use hl.gc over hlc.gc; the latter is always faster.

That is my reasoning as well.

> I have no objections to removing the hl.* grades; clearly no-one is
> using them and doing so would simplify some parts of the system.

OK. If noone else objects, I will start removing them on tuesday.

More information about the developers mailing list