# \#module

**URL:** https://racket.discourse.group/tag/module/57.md

[Latest](https://racket.discourse.group/latest.md) · [Categories](https://racket.discourse.group/categories.md) · [Tags](https://racket.discourse.group/tags.md)

---

## [Namespace-require can't find module in executable](https://racket.discourse.group/t/namespace-require-cant-find-module-in-executable/3592)

<div class="topic-metadata">

**Author:** [@Andy](https://racket.discourse.group/u/Andy)\
**Replies:** 4\
**Last updated:** [February 28, 2025, 2:07pm UTC](https://racket.discourse.group/t/namespace-require-cant-find-module-in-executable/3592 "2025-02-28T14:07:57Z")

</div>

Hello Racket community! I'm trying to use namespace-require, but the executable seems to fail to look up the module, while commandline racket can run it normally. This is the minimal example: test-pkg ├── lib.rkt └── t…

---

## [Getting all available submodules in a module](https://racket.discourse.group/t/getting-all-available-submodules-in-a-module/3542)

<div class="topic-metadata">

**Author:** [@nik](https://racket.discourse.group/u/nik)\
**Replies:** 4\
**Last updated:** [February 5, 2025, 11:46pm UTC](https://racket.discourse.group/t/getting-all-available-submodules-in-a-module/3542 "2025-02-05T23:46:47Z")

</div>

I have a module wherein I defined several submodules. Is there an easy way to get a list of all of the submodules? If I have the following file, example.rkt #lang racket/base (module one racket/base (provide doc) …

---

## [Why modules and when?](https://racket.discourse.group/t/why-modules-and-when/2447)

<div class="topic-metadata">

**Author:** [@thrilway](https://racket.discourse.group/u/thrilway)\
**Replies:** 5\
**Last updated:** [November 1, 2023, 10:04pm UTC](https://racket.discourse.group/t/why-modules-and-when/2447 "2023-11-01T22:04:54Z")

</div>

I'm working on a project in racket—a web app—and I'm wondering whether to make my individual rkt files into modules so the can be imported as, e.g.,(require users), or just leave them as is so they'd be imported as, e.g.,…

---

## [In-out-logged module updated to show results](https://racket.discourse.group/t/in-out-logged-module-updated-to-show-results/563)

<div class="topic-metadata">

**Author:** [@dstorrs](https://racket.discourse.group/u/dstorrs)\
**Replies:** 0\
**Last updated:** [January 12, 2022, 11:00pm UTC](https://racket.discourse.group/t/in-out-logged-module-updated-to-show-results/563 "2022-01-12T23:00:49Z")

</div>

A common pattern I encounter when writing code is that I want to know when control enters a function, what it does while it's there, when it exits, and what it returns. I got tired of writing all this manually, so I cre…

---

## [What would be a "recipe" and lesson plan for building a Racket-like system?](https://racket.discourse.group/t/what-would-be-a-recipe-and-lesson-plan-for-building-a-racket-like-system/554)

<div class="topic-metadata">

**Author:** [@bmitc](https://racket.discourse.group/u/bmitc)\
**Replies:** 3\
**Last updated:** [January 12, 2022, 6:25am UTC](https://racket.discourse.group/t/what-would-be-a-recipe-and-lesson-plan-for-building-a-racket-like-system/554 "2022-01-12T06:25:58Z")

</div>

I am looking for any help, references, etc. that describes how one might take Racket's language building technology and other bits and relevant lessons learned to other languages, ecosystems, or virtual machines (VMs), e…

---

## [TIL: Enforcing contracts with \`contract-out\` from within an embedded test module](https://racket.discourse.group/t/til-enforcing-contracts-with-contract-out-from-within-an-embedded-test-module/525)

<div class="topic-metadata">

**Author:** [@sschwarzer](https://racket.discourse.group/u/sschwarzer)\
**Replies:** 1\
**Last updated:** [January 4, 2022, 10:40pm UTC](https://racket.discourse.group/t/til-enforcing-contracts-with-contract-out-from-within-an-embedded-test-module/525 "2022-01-04T22:40:28Z")

</div>

TL;DR :wink: It's possible to enforce and test contracts defined at the module boundary within a test module in the same file. Do this by require'ing (submod "..") in the test module: (module+ test (require ... …
