| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
provide more useful ambiguous-identifier error output
|
| |\ |
|
| | |
| | |
| | |
| | |
| | | |
the test is only against the first line, but testament doens't
support multi-line error messages yet.
|
|\ \ \
| | | |
| | | | |
Const named tuple unpacking
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Allow for locale-based parsing/formatting of dates
* Updates based on review feedback of PR 11170
DateTimeLocale arrays are now indexed by Month and WeekDay enums.
More sane date used for testing.
Documentation newline.
Case change of DefaultLocale (and make it public)
* Add changelog entry for DateTimeLocale addition to times module
* Use pattern symbols for DateTimeLocale attribute names
|
| | | |
| | | |
| | | |
| | | |
| | | | |
* fixes #11180, forbid casting to unchecked array.
* allow UncheckedArray as param
|
| | | |
| | | |
| | | |
| | | |
| | | | |
* fixes #3456
* add test #3456
|
| | | |
| | | |
| | | |
| | | |
| | | | |
* fixes for ptr array derefence codegen
* fix comments, make diff nicer
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* fixes #9578
* fixed and expanded test
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* Fix loop tuple unpacking in templates
* Add test
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* fix pairs, mpairs, mitems for cstring for JS backend
* add mutation check for pairs and mpairs for strings and seqs
* change the assertion message - modifying (changing elements) is not
a problem, changing the length is
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* fixes #11149
* add test
|
| |_|/
|/| |
| | |
| | |
| | |
| | | |
* add iterator overloads
* add test
|
| | |
| | |
| | |
| | | |
This is an em-dash, not some `--use` flag.
|
|/ / |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
* fixes #1145
* unify error messages
|
| |
| |
| | |
Merging
|
| | |
|
| | |
|
| |
| |
| | |
* fixes #11095
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Revert "Properly wrap discarded statements (#10322)"
This reverts commit 15584879b91e14565156ca140eef1dc100cf34c4.
* add test for implicit discard after defer
* enable t10241 again
* make C++ tests green again
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(#11064)
* remove the restriction that module names need to be unique per Nimble package
* make tests green again
* use the 'response' linker file also on Unix in order to fix megatest
|
| | |
|
| |
| |
| |
| |
| | |
* fixes #10999
* adds a test for #10999
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Revert "Support for stmtListExpr in parser after major keywords. Scaled down version. (#10852)"
This reverts commit 862897dc0f122e374c0e4d44770ffcd8825e51e3.
* redo fix for #4035
* render stmtlistExpr using semicolon
* Revert "render stmtlistExpr using semicolon"
This reverts commit cafb78b8d5b125b5f6ba94248377a1433b3138cb.
* revert test
|
| |
|
| |
|
|
|
|
| |
sink(o.y) needs to compile; activate the tuple unpacking transf.nim bugfix
|
|
|
|
|
|
|
|
|
| |
* use existing sort for CountTable, and
add SortOrder options to CountTable, OrderedTable sort(s)
* add some tests, runnables, etc.
* fix runnable imports
|
|
|
|
|
|
| |
* Extend the fix for #11018 to strings
* Fix testcase
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This plugin provides essential building block for implementing incremental computations in your programs. The idea behind incremental computations is that if you do the same calculation multiple times but with slightly different inputs you don't have to recompute everything from scratch. Also you don't want to adopt special algorithms either, you would like to write your code in standard from scratch manner and get incrementality for free when it is possible.
The plugin computes the digest of the proc bodies, recursively hashing all called procs as well . Such digest with the digest of the argument values gives a good "name" for the result. Terminology loosely follows paper "Incremental Computation with Names" link below. It works well if you have no side effects in your computations. If you have global state in your computations then you will need problem specific workarounds to represent global state in set of "names" . SideEffect tracking in Nim also useful in this topic.
Classical examples:
Dashboard with ticking data. New data arrives non stop and you would like to update the dashboard recomputing only changed outputs.
Excel spreadsheet where user changes one cell and you would like to recompute all cells that are affected by the change, but do not want to recompute every cell in the spreadsheet.
|