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

Implement new Concept Exercise: memory-allocation

Open
#855 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
fsharp
Domain
content

Research direction

Start by reading languages/fsharp/reference/implementing-a-concept-exercise.md and comparing languages/fsharp/exercises/concept/numbers/.meta/design.md and .meta/config.json with the linked v3 guidance. Use reference/concepts/memory-allocation.md and the listed learning objectives to shape the exercise, then confirm the completed exercise and metadata follow the F# track conventions.

Written by the indexing model from the issue text.

Description

x:action/create x:knowledge/intermediate x:module/concept-exercise x:size/large x:type/content

This issue describes how to implement the memory-allocation concept exercise for the F# track.

Getting started

Please please please read the docs before starting. Posting PRs without reading these docs will be a lot more frustrating for you during the review cycle, and exhaust Exercism's maintainers' time. So, before diving into the implementation, please read up on the following documents:

Please also watch the following video:

Goal

The goal of this exercise is to teach the student the basics of the Concept of Memory Allocation in F#.

Learning objectives

  • Know what the stack and heap are.
  • Know what the garbage collector is.
  • Know how the stack and heap are different.
  • Know what the large object heap is.
  • Know what reference and value types are.
  • Know how reference and value types relate to the stack and heap.
  • Know how to make a discriminated union, record, tuple or class a struct.

Out of scope

  • Memory locality.
  • Memory pooling.
  • Pointer semantics.
  • Span<T> and Memory<T>
  • Readonly semantics and by reference arguments.
  • Discussion of profiling tools (referring to them is fine).

Concepts

The Concepts this exercise unlocks are:

  • memory-allocation: know what the stack and heap are; know what the garbage collector is; know how the stack and heap are different; know what the large object heap is; know what reference and value types are; know how reference and value types relate to the stack and heap; know how to make a discriminated union, record, tuple or class a struct.

Prerequisites

This exercise's prerequisites Concepts are:

  • classes: know how to define a class.
  • records: know how to define a record.
  • tuples: know how to define a tuple.
  • discriminated-unions: know how to define a discriminated union.
  • attributes: know how to add attributes.

Any data types used in this exercise (e.g. strings or integers) should also be added as prerequisites.

Resources to refer to

Hints

The following links all use C# as their language, but the concepts apply equally as well to F#:

After

The following links all use C# as their language, but the concepts apply equally as well to F#:

Representer

This exercise does not require any specific representation logic to be added to the representer.

Analyzer

This exercise does not require any specific logic to be added to the analyzer.

Implementing

To implement this exercise, please follow these instructions.

Help

If you have any questions while implementing the exercise, please post the questions as comments in this issue.

Dominant language
F#
Stars
118
Forks
113
Avg merge
1d 16h
Merged PRs (30d)
3

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 exercism/fsharp

All issues in exercism/fsharp

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.