Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

math functions conflicts with types

Open
#190 5 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
computer-graphics

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.

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

Dominant language
C#
Stars
1.4k
Forks
159
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Unity-Technologies/Unity.Mathematics

All issues in Unity-Technologies/Unity.Mathematics

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.