For now, units only compiles on linux operating system. This should be fixed

Output when running with --stacktrace
Output when running with --info

For example speed of light, absolute zero temperature, etc.

energy is mass * length * length / duration * duration.

Regarding Duration,

In Days and Years (as you do in all classes that are NumericValues),
you pass the unit tag first (duration_tag), and then the scale tag (days_tag).
In classes that are created with Duration, you pass the scale tag before the unit tag
F.E:

• using Minutes = Duration<std::chrono::minutes, minutes_tag, duration_tag>;
• using Days = NumericValue<days_tag, duration_tag>;

• Add multiply type
• Add multiply function

Look at whatsapp darling

Including basic usage and units casting

a stupid typo

For now, just mol

In Durations, does NumericValue's "explicit-ness" pass to Duration's constructor?

void doSomething(Seconds s) { /* */ };
doSomething(3);

Would this work?

• Add ratio unit types
• Add ratio function

for now, just pascal

for example: kilograms per cubic meter

Need to add the followings:

• generating conversion test
• compile generator before generating

For some reason, conversions.md is generated differently, which makes the output looks wrong.

Before:

After:

I suspect it's possibly one of the last commits regarding the .stg, maybe it's an HTML issue.

Side note 1: Should change "MANUALY" to "MANUALLY"
Side note 2: Maybe comment out the "don't touch auto-generated files" decleration?
It should be visible to the developer, not to the user.

Regarding Duration,

Lines 53-55 and 64-66 calculate scale based on conversions from chrono classes for minutes_tag and hours_tag, unlike days_tag and years_tag that are calculated based on their previous tags scale.

Do you do that because there's no suitable method for these scales? Perhaps it's better for clarity to simplify calculation in minutes_tag and hours_tag instead of using conversions from chrono?

Also, you can make a template method out of what's going on in the lines I've stated above, it might help in clarity if you want to keep conversions based on chrono.

when defining a new ratio type in units.json there is no validation on the units in the ratio.

Hello loser, you should probably create a README.md file for introduction and basic usage, and probably a docs folder with .md files that document stuff

FAILURE: Build failed with an exception.

• Where:
  Build file 'C:\Repositories\units\build.gradle' line: 47

• What went wrong:
  Execution failed for task ':generate'.

Failed to capture snapshot of output files for task 'copyGeneratedSupportedUnits' property 'destinationDir' during up-to-date check.

• Try:
  Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED in 34s
1 actionable task: 1 executed

Full output
Full output with --stacktrace