From e50501448314f3f425e1eb68d6d7d842e716ca4a Mon Sep 17 00:00:00 2001 From: Jaisurya Nanduri Date: Tue, 9 Jul 2024 22:19:27 +0000 Subject: [PATCH] sample text --- doc/src/challenges/0001-core-transmutation.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/src/challenges/0001-core-transmutation.md b/doc/src/challenges/0001-core-transmutation.md index 3a71c0c12ff29..88a68ffb29205 100644 --- a/doc/src/challenges/0001-core-transmutation.md +++ b/doc/src/challenges/0001-core-transmutation.md @@ -144,3 +144,5 @@ The list of methods and intrinsics was gathered by surveying the call-graph (sol As mentioned in the assumptions, some (large) classes of methods were omitted from the challenge, either because 1. they encompassed a large API surface (e.g. `core::num`) that deserved separate treatment, 2. they had an enormous number of callers that would deserve separate treatment (e.g. `core::str::from_utf8_unchecked`), or 3. they interact with aspects of the Rust memory model that still need to be better understood by reasoning tools (e.g. the provenance APIs). You can see the [call graph produced by the survey here](https://hackmd.io/PYQNIL_aTxK0N6-AltxfbQ). + +blah blah.