m4rs-mt/ILGPU - Open Source PR Review Scorecard

ILGPU JIT Compiler for high-performance .Net GPU programs

C-Rank Grade: B (Solid) - 40/100

External PR Merge Rate: -

Response Time: -

First Timer Success: -

Frequently Asked Questions

Is m4rs-mt/ILGPU welcoming to first-time open-source contributors?

m4rs-mt/ILGPU has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in m4rs-mt/ILGPU respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 39.7 C-Rank™ score (B Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 39.7 places m4rs-mt/ILGPU in the B tier.

What is the external contributor pull request merge rate for m4rs-mt/ILGPU?

The external contributor pull request merge rate for m4rs-mt/ILGPU is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in m4rs-mt/ILGPU?

m4rs-mt/ILGPU currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

m4rs-mt
m4rs-mt/ILGPUB•Solid1.8k
GitHub
Back to Explorer
m4rs-mt

m4rs-mt/ILGPU

1,758
Active (30d)B•Solid(40/100)Low Sample (<20 PRs)C#

ILGPU JIT Compiler for high-performance .Net GPU programs

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.6/10
Patience Score
8.2/10
Nitpick Rate
25%

Collaborative maintainer environment in m4rs-mt/ILGPU. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in m4rs-mt/ILGPU focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Link the issue and include reproduction context in the PR
  • •Update docs or README when behavior changes
  • •Add or update tests for changed behavior before requesting review

Top PR Friction Pitfalls (Don'ts)

  • •Do not open context-free PRs
  • •Do not ship user-facing changes without matching docs
  • •Do not leave requested test coverage unresolved
Response Velocity
-
No reviewer activity recorded

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
0.0%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
0.0%
Merge Gauge
0.0%
1st-Timer
Community Vibe0/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for m4rs-mt/ILGPU
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/m4rs-mt/ILGPU)](https://getmerged.abhishekco.de/m4rs-mt/ILGPU?utm_source=github&utm_medium=badge)

Active Good First Issues (2)

View on GitHub

Question I experimenting with ILGPU for accelerating some computations on large point clouds. When I use Allocate3DDenseXY it throws and exception CL_INVALID_BUFFER_SIZE, which seems to be because the buffer I'm trying to allocate is too large (1024 x 1024 x 1024 floats). Is there a way that I can access CL_DEVICE_MAX_MEM_ALLOC_SIZE so that I can efficiently process the data in chunks? I don't see anything about it in the documentation. The GPU it's chosen (using ctx.GetPreferredDevice) is the integrated Intel one, which is surprising given I have a powerful NVIDIA GPU. Environment ILGPU version: 1.5.3 .NET 10 Operating system: Windows 11 Hardware (if GPU-related): Intel(R) RaptorLake-S Mobile Graphics Controller Additional context No response

📅 Opened Jul 20, 2026💬 0 comments
Quality: 40/100Contribute

Question I need to run a method created dynamically. DynamicMethod dm=new DynamicMethod("Test", typeof(void),new Type[]{typeof(Index1D),typeof(ArrayView<Single>)},typeof(Program)); var il= dm.GetILGenerator(); il.Emit(OpCodes.Ret); var del=dm.CreateDelegate<Action<Index1D,ArrayView<float>>>(); /* equals to: static void Test( Index1D index,ArrayView<float> buffer) // A view of floats to store float results from GPUMath { return; } */ using var context = Context.CreateDefault(); using var accelerator = context.GetPreferredDevice(preferCPU: true).CreateAccelerator(context); var kernel = accelerator.LoadAutoGroupedStreamKernel(del); using var buffer = accelerator.Allocate1D<float>(128); kernel((int)buffer.Length, buffer.View); However, exception System.NotSupportedException: Derived classes must provide an implementation. takes place. Is there any way to compile a dynamically created method with ILGpu? And there's no "Derived classes" I think Environment ILGPU

📅 Opened Feb 12, 2026💬 3 comments
Quality: 45/100Contribute
Looking for more C# beginner tasks?Explore C# GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for m4rs-mt/ILGPU

When evaluating whether to contribute to m4rs-mt/ILGPU, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of m4rs-mt/ILGPU acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to m4rs-mt/ILGPU

01

Is m4rs-mt/ILGPU welcoming to first-time open-source contributors?

m4rs-mt/ILGPU has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 39.7 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 39.7 places m4rs-mt/ILGPU in the Solid tier.

04

What is the external contributor pull request merge rate for m4rs-mt/ILGPU?

The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in m4rs-mt/ILGPU?

Yes, m4rs-mt/ILGPU currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for m4rs-mt/ILGPU are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.