| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
- latest sentry, tar-stream, which, some yamljs versions
- latest eslint-* stuff
- latest webpack manifest
- Applies all the automatic fixes for newer lint rules
- Bump the webpack version
applies new tslint stuff
|
| |
|
| |
LDC does not quite copy Clang cmdline options, so it's best to implement its own parser.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
* The Grand Reformat
- everything made prettier...literally
- some tweaks to include a few more files, including documentation
- minor changes to format style
- some tiny `// prettier-ignore` changes to keep a few things the way we like them
- a couple of super minor tweaks to embedded document types to ensure they format correctly
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* All semver comparisons now ensure it's safe to do so
* Oops, use correct class
* Remove leftover import
* Leave the Zig fixes for another PR
* Fix linter
* Fix test issues
* Make linter happy, yet again
* What?
* Address PR review
|
| |
|
| |
This changes the default LDC compile flag from `-g` to `-gline-tables-only`, such that the LLVM IR output does not contain `call void @llvm.dbg.declare` calls that (I think) most users are not interested in. The old behavior can be restored by the user by passing `-g` (I think users are much more familiar with the `-g` option than the `-gline-tables-only` option). Line information is preserved so users can still see what IR lines correspond to user code lines.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The largest changes here are:
- enforcing single quotes for strings
- enforcing trailing commas where possible
In addition to those we have enabled several eslint plugins:
- plugin:requirejs/recommended, to enforce some conventions in require statements
- plugin:node/recommended, to enforce correct usage of various node.js APIs
- plugin:unicorn/recommended, which contains a pretty mixed bag of useful rules
This PR attempts to not change code behavior when possible. In cases where fixing
existing code would change semantics, a linting exclusion has been placed in the
code base to silence the error. You can find these by searching for `eslint-disable-next-line`.
Co-authored-by: Austin Morton <austinpmorton@gmail.com>
|
| |
|
|
|
|
|
|
| |
Async-ify base-compiler
* Adds async to a number of methods
* Breaks 'compile' into a few smaller methods for readability
* Remove a few (seemingly!) unnecessary `Promise.all([x])`
|
| | |
|
| |
|
|
| |
closes #497
|
| | |
|
| | |
|
| |
|
|
| |
Closes #1088
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
I forgot to run the hook installation after a clean reclone...
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Somewhat compilant!
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Mitigates #765. Execution support should need this too, as not to
run the program twice
|
| | |
|
| | |
|
| |
|
|
|
| |
Not saying it works, but if you hack few more things, you can start
to use it. Commiting just in case
|
| |
|
|
| |
add/remove options per compiler such as for rust where we need to not add the --emit argument if the user has passed us one
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
