Unity-Technologies / Unity-Technologies/Unity.Mathematics
math functions conflicts with types
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.4k
- Forks
- 159
- PR merge metrics
- No merged PRs in 30d
Description
using static Unity.Mathematics.math; will cause conflicts with types like float3 type, preventing you from using float3.zero ('math.float3(float, float, float)' is a method, which is not valid in the given context)
naming of those functions should be reconsidered
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files or tests. Start by reproducing the using-static example and inspect the public math functions and vector-type declarations to identify the conflicting names. Define the intended naming scope before changing the API, then verify that float3.zero and related type members remain usable without conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- computer-graphics
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100