7,013 Commits over 3,561 Days - 0.08cph!
Some cleanup, experimenting with multiple layers
Re-use MarchingSquaresMeshWriter instances
Physics shape generation
Some mesh writer simplification
Encode each distance as a byte rather than a float
Front and back mesh generation
Allow configuring maximum distance in SDF
Another mesh generation fix
Add CornerRadius property to BoxSdf
Some mesh generation fixes
Some 2D SDF boilerplate, WIP mesh generation
Rename VoxelVolume -> MarchingCubesEntity
Some dumb multi-threading
Rainbow blobs
Preview matches brush colour
Subtracting will always ray cast
Capsule SDF type for drawing lines
Failing test reproducing sboxgame/issues#3227
Fixed sboxgame/issues#3227
Failing test reproducing sboxgame/issues#3227
Fixed sboxgame/issues#3227
Failing test reproducing sboxgame/issues#3227
Warn about missing input actions once
Fixed documentation of Compiler.Name
Failing test reproducing #996
Better generic method resolution, fixes #996
Possible fix for sboxgame/issues#3227
Make RPC code gen deterministic
Better generic method resolution, fixes #996
Possible fix for sboxgame/issues#3227
Warn about missing input actions once
Fixed documentation of Compiler.Name
Failing test reproducing #996
Warn about missing input actions once
Fixed documentation of Compiler.Name
Failing test reproducing #996
Voxel shader texture scale tweak
Blob tool keeps editing at distance of first ray on click
Consistent indentation
Fixed VoxelChunk bounds
Addon packages should reference package.base too
When loading multiple packages, sort by references
Make sure that a referenced package is loaded before the packages that reference it.
Possible fix for #996
Added test for Package.SortByReferences()
Initial commit
Added default material
Allow resolving newer versions of assemblies in AccessControl
Fixed publishing addons referencing libraries
* Added helper DistinctReferences / DistinctPackageReferences properties to include all system / package references respectively.
* For addon packages, DistinctPackageReferences will include the parent package.
Package reference fixes (#965)
* Use PackageReference for referencing packages, References for referencing assemblies
* Fixed test passing for the wrong reason
* Rename Compiler.PackageReference to PackageReferences
* Don't fast hotload if a referenced assembly has changed
* More assembly / package reference strictness
* Made generic method resolving / comparing stricter
* We need to re-resolve all member references in fast-hotloaded methods
* More precise logic when deciding if a referencing assembly can be fast-hotloaded
* Constructor resolution regression fix
* Some cleanup in ILGeneratorExtensions
* Hotload.GetMethods helper now matches name
* Access control now caches assembly definitions by name + version
* Assert that the correct assembly definition version is resolved
* Keep exactly the outgoing assembly definition cached, but dispose older versions
* Clean up AccessControl.Resolve a bit
* WIP referencing fast-hotloaded assembly fix
* Fixed unloading IsolatedAssemblyContexts during fast hotload
* Remove some logging
* Fix menu breaking after hotload
* WIP force-reload assemblies that depend on a changed package
* Allow resolving newer assembly versions
* PackageLoader.LoadAssemblyFromPackage cleanup
* Only force an assembly reload if dependent package did a full hotload
* Fix exception in ContextTools.DetermineContext in fast hotloaded methods
* Init TypeLibrary in TestUI.Panels.PanelTests
* Description codegen: just allow multiple [Description] instead of being non-deterministic
Use PackageReference for referencing packages, References for referencing assemblies
The fuzzy search in FindCompilerByName was getting messy, so that's replaced with FindCompilerByAssemblyName / FindCompilerByPackageName.
Also this fixes changed library packages not marking dependent compilers for recompile (#956)
Fixed test passing for the wrong reason
Rename Compiler.PackageReference to PackageReferences
Don't fast hotload if a referenced assembly has changed
More assembly / package reference strictness
Made generic method resolving / comparing stricter
We need to re-resolve all member references in fast-hotloaded methods
This fixes references to types from fast-hotloaded referenced assemblies
More precise logic when deciding if a referencing assembly can be fast-hotloaded
Constructor resolution regression fix
Some cleanup in ILGeneratorExtensions
Hotload.GetMethods helper now matches name
Access control now caches assembly definitions by name + version
Fixes issues where hotload requires a specific old version
Assert that the correct assembly definition version is resolved
Keep exactly the outgoing assembly definition cached, but dispose older versions
Clean up AccessControl.Resolve a bit
WIP referencing fast-hotloaded assembly fix
Fixed unloading IsolatedAssemblyContexts during fast hotload
In a fast hotload, DON'T unload outgoing, but DO unload incoming after the fast hotload
Remove some logging
Fix menu breaking after hotload
WIP force-reload assemblies that depend on a changed package
Allow resolving newer assembly versions
PackageLoader.LoadAssemblyFromPackage cleanup
Only force an assembly reload if dependent package did a full hotload
Fix exception in ContextTools.DetermineContext in fast hotloaded methods
Init TypeLibrary in TestUI.Panels.PanelTests
Description codegen: just allow multiple [Description] instead of being non-deterministic
Partial class declarations were being handled by the first worker to process them, which generated code non-deterministically. This meant fast-hotload would often detect changes it couldn't handle when doing syntax tree comparisons.
Description codegen: just allow multiple [Description] instead of being non-deterministic
Partial class declarations were being handled by the first worker to process them, which generated code non-deterministically. This meant fast-hotload would often detect changes it couldn't handle when doing syntax tree comparisons.
Use PackageReference for referencing packages, References for referencing assemblies
The fuzzy search in FindCompilerByName was getting messy, so that's replaced with FindCompilerByAssemblyName / FindCompilerByPackageName.
Also this fixes changed library packages not marking dependent compilers for recompile (#956)
Fixed test passing for the wrong reason
Rename Compiler.PackageReference to PackageReferences
Don't fast hotload if a referenced assembly has changed
More assembly / package reference strictness
Made generic method resolving / comparing stricter
We need to re-resolve all member references in fast-hotloaded methods
This fixes references to types from fast-hotloaded referenced assemblies
More precise logic when deciding if a referencing assembly can be fast-hotloaded
Constructor resolution regression fix
Some cleanup in ILGeneratorExtensions
Hotload.GetMethods helper now matches name
Access control now caches assembly definitions by name + version
Fixes issues where hotload requires a specific old version
Assert that the correct assembly definition version is resolved
Keep exactly the outgoing assembly definition cached, but dispose older versions
Clean up AccessControl.Resolve a bit
WIP referencing fast-hotloaded assembly fix
Fixed unloading IsolatedAssemblyContexts during fast hotload
In a fast hotload, DON'T unload outgoing, but DO unload incoming after the fast hotload
Remove some logging
Fix menu breaking after hotload
WIP force-reload assemblies that depend on a changed package
Allow resolving newer assembly versions
PackageLoader.LoadAssemblyFromPackage cleanup
Only force an assembly reload if dependent package did a full hotload
Fix exception in ContextTools.DetermineContext in fast hotloaded methods
Init TypeLibrary in TestUI.Panels.PanelTests
Only force an assembly reload if dependent package did a full hotload
Fix exception in ContextTools.DetermineContext in fast hotloaded methods
Fix menu breaking after hotload
WIP force-reload assemblies that depend on a changed package
Allow resolving newer assembly versions
PackageLoader.LoadAssemblyFromPackage cleanup
Fixed unloading IsolatedAssemblyContexts during fast hotload
In a fast hotload, DON'T unload outgoing, but DO unload incoming after the fast hotload
Use PackageReference for referencing packages, References for referencing assemblies
The fuzzy search in FindCompilerByName was getting messy, so that's replaced with FindCompilerByAssemblyName / FindCompilerByPackageName.
Also this fixes changed library packages not marking dependent compilers for recompile (#956)
Fixed test passing for the wrong reason
Rename Compiler.PackageReference to PackageReferences
Don't fast hotload if a referenced assembly has changed
More assembly / package reference strictness
Made generic method resolving / comparing stricter
We need to re-resolve all member references in fast-hotloaded methods
This fixes references to types from fast-hotloaded referenced assemblies
More precise logic when deciding if a referencing assembly can be fast-hotloaded
Constructor resolution regression fix
Some cleanup in ILGeneratorExtensions
Hotload.GetMethods helper now matches name
Access control now caches assembly definitions by name + version
Fixes issues where hotload requires a specific old version
Assert that the correct assembly definition version is resolved
Keep exactly the outgoing assembly definition cached, but dispose older versions
Clean up AccessControl.Resolve a bit
WIP referencing fast-hotloaded assembly fix
Add Filter property to SkipHotloadAttribute
Allow skipping to be conditional on realm (tools / menu / server / client / test)
Don't skip IMenuAddon.Current during menu hotloads
Use PackageReference for referencing packages, References for referencing assemblies
The fuzzy search in FindCompilerByName was getting messy, so that's replaced with FindCompilerByAssemblyName / FindCompilerByPackageName.
Also this fixes changed library packages not marking dependent compilers for recompile (#956)
Fixed test passing for the wrong reason
Rename Compiler.PackageReference to PackageReferences
Don't fast hotload if a referenced assembly has changed
More assembly / package reference strictness
Made generic method resolving / comparing stricter
We need to re-resolve all member references in fast-hotloaded methods
This fixes references to types from fast-hotloaded referenced assemblies
More precise logic when deciding if a referencing assembly can be fast-hotloaded
Constructor resolution regression fix
Some cleanup in ILGeneratorExtensions
Hotload.GetMethods helper now matches name
Access control now caches assembly definitions by name + version
Fixes issues where hotload requires a specific old version
Assert that the correct assembly definition version is resolved
Keep exactly the outgoing assembly definition cached, but dispose older versions
Clean up AccessControl.Resolve a bit
More assembly / package reference strictness
Made generic method resolving / comparing stricter
We need to re-resolve all member references in fast-hotloaded methods
This fixes references to types from fast-hotloaded referenced assemblies
More precise logic when deciding if a referencing assembly can be fast-hotloaded
Use PackageReference for referencing packages, References for referencing assemblies
The fuzzy search in FindCompilerByName was getting messy, so that's replaced with FindCompilerByAssemblyName / FindCompilerByPackageName.
Also this fixes changed library packages not marking dependent compilers for recompile (#956)
Fixed test passing for the wrong reason
Rename Compiler.PackageReference to PackageReferences
Don't fast hotload if a referenced assembly has changed
Don't fast hotload if a referenced assembly has changed
Fixed test passing for the wrong reason
Rename Compiler.PackageReference to PackageReferences
Use PackageReference for referencing packages, References for referencing assemblies
The fuzzy search in FindCompilerByName was getting messy, so that's replaced with FindCompilerByAssemblyName / FindCompilerByPackageName.
Also this fixes changed library packages not marking dependent compilers for recompile (#956)
Test for Assembly.GetExecutingAssembly()
Failing test reproducing #957
Fix variable types
Although this seems to be non-deterministic, with some cache breaking later replacements
Stricter GenericReference2 test
Fixed #957 by clearing MonoMod's reflection cache
Fix variable types
Although this seems to be non-deterministic, with some cache breaking later replacements
Stricter GenericReference2 test
Fixed #957 by clearing MonoMod's reflection cache
Test for Assembly.GetExecutingAssembly()
Failing test reproducing #957
Don't sort generated code blocks inside class groups!
Whoops
