Colin Seymour

> Is their insufficient usage of this language to be considered for inclusion right now (re: label of `pending popularity`)? Yup. Usage of _all_ extensions being added needs to meet...

> Would creating an example piece of code (in our case a contract) that is not meant to work (or be a good example). Rather it should be written for...

From a quick glance, things are looking good now though usage is still too low when we [exclude forks and the huff-language user](https://github.com/search?q=%28path%3A*.huff+OR+path%3A*.Huff%29+NOT+is%3Afork+NOT+user%3Ahuff-language+&type=code). I'll keep reviewing the usage with each...

Reviews of all pending popularity PRs takes place when I'm preparing for the next release. This will be reviewed again then.

I need to do it before my colleagues start preparing the next release of Enterprise Server which starts around the middle of the month, so it'll probably be sometime next...

As previously stated, nothing more is needed on this PR and I review popularity with each release. Our requirements still weren't met when I reviewed for the last release. I...

> So, can you please add recognition for the '.def' file extension. > > I had reported this many years ago, but apparently nothing has happened since and I can't...

> However, both .def and .mod are already in those files, so this will not fix the issue of not recognising the file extension. > > I am assuming there...

Oh yes, and we need to know the licence of all samples (they need to be covered by an open source licence)… the repo you referenced has no licence so...

> 1. Can you outline here if both Aleo Instructions and Leo need to meet the 2000 file requirement or if Aleo Instructions only needs 200 files? Aleo Instructions files...