tanya, branch v0.8.1 GC-free, high-performance D library: Containers, networking, metaprogramming, memory management, utilities. Fix list assertions for release build 2018-04-18T12:23:12+00:00 Eugen Wissner belka@caraus.de 2018-04-18T12:23:12+00:00 964a7af32f709b311ac549808ae331827bdcb480 






Remove deprecated traits and queue
2018-04-18T04:34:28+00:00

Eugen Wissner
belka@caraus.de

2018-04-18T04:34:28+00:00

40c961867eddb7e53d9691baf8b7ae1a68ccaf3b












Implement DList.popFirstOf and DList.popLastOf
2018-04-17T12:46:12+00:00

Eugen Wissner
belka@caraus.de

2018-04-17T12:46:05+00:00

3fee712c6ce55ab2342c236c2120d64bf0f9c215

Fix #37.





Fix #37.







Remove support for dmd 2.076.1
2018-04-15T04:50:37+00:00

Eugen Wissner
belka@caraus.de

2018-04-14T14:19:23+00:00

012c2d4c1801311847648c2f684ae9ab26870c31












Implement SList.popFirstOf
2018-04-14T14:15:35+00:00

Eugen Wissner
belka@caraus.de

2018-04-12T17:35:59+00:00

d267a9cc645f1219203bd43e046dc07b4a1fc520

Fix #36.

Slicing for the SList on top of the existing SRange would be inefficent.
There would be two cases:
- Range iterates till the end of the list.
- Range iterates till some element "end".

If both cases are implemented in the same range, this range should check
for both conditions (end of the list and "begin == end") instead of only
one (end of the list).

Introducing a different range is undesirable since all containers have
currently only one range.





Fix #36.

Slicing for the SList on top of the existing SRange would be inefficent.
There would be two cases:
- Range iterates till the end of the list.
- Range iterates till some element "end".

If both cases are implemented in the same range, this range should check
for both conditions (end of the list and "begin == end") instead of only
one (end of the list).

Introducing a different range is undesirable since all containers have
currently only one range.







Add dscanner style check to CI
2018-04-12T15:14:22+00:00

Eugen Wissner
belka@caraus.de

2018-04-11T19:21:30+00:00

ddb02e41ebc9470c183ccb0d4a256a4eb2f14968

Fix #38.





Fix #38.







Fix import order in math.random
2018-04-08T03:59:14+00:00

Eugen Wissner
belka@caraus.de

2018-04-08T03:59:14+00:00

d157e88b7afa397270faf2de84dc90187c6ec2e8












Add missing tail isn't null assertion
2018-04-07T17:20:08+00:00

Eugen Wissner
belka@caraus.de

2018-04-07T17:20:08+00:00

d5064fa2b2bd98fa955e95eef0cf8b11d0aad341












Remove support for moveFront/moveBack/moveAt
2018-04-03T19:44:50+00:00

Eugen Wissner
belka@caraus.de

2018-04-03T19:44:50+00:00

f15a90543f48055ec9cfe31048e6e5cbd48b7b41

Range elements are movable (mobile) if they are returned by reference
and can be moved or if the elements doesn't define an elaborate postblit
constructor. Allowing to define custom moveFront/moveBack/moveAt makes
the range definition more complex (particulary writing range adapters)
without a good reason.





Range elements are movable (mobile) if they are returned by reference
and can be moved or if the elements doesn't define an elaborate postblit
constructor. Allowing to define custom moveFront/moveBack/moveAt makes
the range definition more complex (particulary writing range adapters)
without a good reason.







Fix #29
2018-04-01T08:34:18+00:00

Eugen Wissner
belka@caraus.de

2018-04-01T08:34:18+00:00

a0ac8355f9adc1dbb211d516383b57868773ac61