1
0
mirror of https://github.com/oliverbooth/X10D synced 2024-11-25 15:38:46 +00:00
Commit Graph

1083 Commits

Author SHA1 Message Date
da220c2242
build: partial revert 58c333a173 (#75)
Removes the reference to JetBrains.dotCover.MSBuild.
2023-04-02 19:40:25 +01:00
2439b3a3cd
[ci skip] style(ci): remove redundant empty line 2023-04-02 17:44:16 +01:00
fb20e4d1e9
[ci skip] ci: copy artifacts before git diff
Also removes redundant shell specifier on git diff step. GitHub uses bash by default.
2023-04-02 17:42:59 +01:00
ebc8734410
build: partial revert 58c333a173 (#75)) 2023-04-02 17:34:24 +01:00
a093e91502
[ci skip] ci: cd upm before git diff 2023-04-02 17:28:58 +01:00
6fd7f8d84c
ci: only commit if working tree contains changes 2023-04-02 17:25:56 +01:00
2bfe0b24d0
[ci skip] ci: add trace logging for upm package.json generator 2023-04-02 17:16:18 +01:00
e2a608f11d
build: output debug symbols for all projects (#75) 2023-04-02 17:06:18 +01:00
e4431fca5f
ci: specify configuration for build steps
nightly should use Debug configuration
2023-04-02 16:46:34 +01:00
043aca8777
ci: skip redundant build steps
dotnet build now uses --no-restore flag, and dotnet pack now uses --no-build flag, since these steps are already done beforehand.
2023-04-02 16:43:31 +01:00
2c01b0e23a
build: remove Debug properties in test csproj
I believe these properties to be the cause of an issue with symbol verification when publishing X10D to nuget.org. I will report with status after this nightly run.
2023-04-02 15:53:54 +01:00
3b47c67a43
ci: upload dotnet pack artifacts 2023-04-02 15:44:10 +01:00
fdc0c6aa35
perf: fix performance of intrisics
This changes removes the CPU-arch support provider interfaces that were introduced with 87b6dbdd56. That commit worsened the performance of the intrinsic methods because it resulted in a box when upcasting the System_SupportProvider value type to an interface, removing the potential for JIT to optimise the code path.
2023-04-02 15:17:28 +01:00
77836d51fc
fix(test): fix ref as of bc3dedfa7d 2023-04-02 04:54:58 +01:00
6b1dc2837a
test: bring coverage to 100% for Collections, Linq, Math, and Text 2023-04-02 04:16:33 +01:00
918b0b7612
ci: exclude cpu-arch support providers from coverage 2023-04-02 03:44:35 +01:00
daff6ee3fe
fix: suppress .NET analyzer for test project 2023-04-02 03:31:37 +01:00
bf73ecce32
test: add unit tests for ServiceCollectionExtensions 2023-04-02 03:31:19 +01:00
ceaa254d7a
docs/perf: throw for null input 2023-04-02 03:12:04 +01:00
3d69cf362d
fix: CLSCompliant(false) for X10D.Unity 2023-04-02 03:11:22 +01:00
7e7825a170
fix: suppress CA1000
This analyzer warning does not apply here.
2023-04-02 03:10:58 +01:00
bc3dedfa7d
fix: rename DebugEx to DebugUtility
Prevents .NET analysers from throwing errors.
2023-04-02 03:10:36 +01:00
08a4df0c64
perf: remove local method, exclude coverage for default arm 2023-04-02 02:56:50 +01:00
85f4e8c733
test: bring coverage to 100% for AddOrUpdate 2023-04-02 01:16:12 +01:00
bfd3a5663d
[ci skip] ci: enable .NET analyzers for all projects 2023-04-02 01:11:14 +01:00
c0bd7e0032
ci: exclude uncoverable projects from coverage 2023-04-02 01:07:35 +01:00
427563bfdb
[ci skip] test: CollectCoverage:true 2023-04-02 01:07:01 +01:00
e5ec06cfe5
[ci skip] test: output debug symbols 2023-04-02 01:06:38 +01:00
58c333a173
ci: exclude default arm of Rune.Repeat from coverage 2023-04-02 01:05:27 +01:00
95cd3e8cbc
test: bring coverage to 100% for X10D.Collections.SpanExtensions 2023-04-02 00:36:31 +01:00
f10ff4a36c
test: add tests for Span<T>.Count 2023-04-02 00:18:47 +01:00
586057ba3d
test: add tests for ReverseElements (#73) 2023-04-01 23:48:08 +01:00
6f16c0df3c
test: add tests for CorrectBoolean (#73) 2023-04-01 23:40:41 +01:00
34c49a2228
fix: fix bug introduced by d29663f081
Since value is a ref returned value, mutating it before returning was actually intended behaviour, since the reassignment causes the dictionary value to be mutated too.

Also, what game was this ref watching?!
2023-04-01 22:32:02 +01:00
9df0fde96d
ci(dotnet): run framework-specific tests separately
This change also specifies multiple dotnet-version values for the setup-dotnet step.
2023-04-01 22:21:14 +01:00
8a4e053c85
fix: expose internals to X10D.Tests project 2023-04-01 22:12:16 +01:00
d29663f081
style: cleanup DictionaryExtensions
* Explicit type is used where type is not evident.
* Conditions are inlined with a ternary and the return value is used directly.
* System.Runtime.InteropServices is only imported for .NET >= 6.0
2023-04-01 22:05:10 +01:00
b79435211a
style: remove redundant else branches 2023-04-01 22:01:07 +01:00
d7bf9d1788
style(test): remove throws of NotImplementedException 2023-04-01 22:00:40 +01:00
23282db3a9
fix(test): import X10D.Core for NextSingle to work on < net6.0 2023-04-01 22:00:11 +01:00
87b6dbdd56
test: bring coverage to 100% for integer Unpack (#70) 2023-04-01 21:56:45 +01:00
5f21a2102d
feat: pack README.md in nupkg 2023-04-01 21:16:57 +01:00
ca5f95bbf6
test: test RuneExtensions for .NET >= 5 2023-04-01 18:59:24 +01:00
e52e9096e0
feat: expose ComplexSqrt to all frameworks 2023-04-01 18:54:04 +01:00
1acee3bf72
fix(test): fix incorrect date being returned for .NET Standard 2.1 2023-04-01 18:20:44 +01:00
5714ef73c1
test: 100% coverage on stream Read/Write methods 2023-04-01 18:17:50 +01:00
fa2236e72a
fix: write float, not double, in Stream.WriteSingle
This was a side effect of 2815c505c3 since I had copy/pasted the blocks. Oops.
2023-04-01 17:14:46 +01:00
990f860b39
perf: accept ReadOnlySpan<byte> in WriteInternal
This method does not mutate the input span in any way, and so its input can be read-only.
2023-04-01 17:11:47 +01:00
2815c505c3
fix: fix incorrect float/double being written for netstandard2.1
The call to _To_Bits yields the result containing the same bytes, but not the same value. This value was then stored as-is into the parameter, which causes a conversion on how the value is stored, ultimately causing the wrong value to be written to the stream.
2023-04-01 17:11:05 +01:00
677259b91c
fix: fixed Stream.ReadSingle returning wrong type
ReadSingle previously returned a double, and this never failed unit tests since float -> double is a widening conversion, with values being comparable.
2023-04-01 17:08:34 +01:00