PR suggestions in order to achieve platform compatability

Open
#1,181 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
c

Research direction

The issue names no files, tests, or entry points. First clarify which platforms and architectures are involved, what changes can be disclosed despite the NDA, and how the proposed work should be contributed; done should include an agreed contribution path and a sufficiently specific scope.

Written by the indexing model from the issue text.

Description

I have changes to mimalloc that I would like to introduce in order form more platform and architecture coverage.
As it is, I am bound to NDA's and cannot go into details more specifically than that. How would I best go to make a PR? I am using dev3

Dominant language
C
Stars
13.6k
Forks
1.2k
Avg merge
18h 12m
Merged PRs (30d)
20

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 microsoft/mimalloc

All issues in microsoft/mimalloc

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.