├── .gitignore ├── src ├── stdout.js.mbt ├── stdout.mbt ├── stdout_native.c ├── stdout.native.mbt ├── moon.pkg.json ├── stdout.wasm.mbt └── README.mbt.md ├── moon.mod.json ├── README.md ├── Agents.md └── LICENSE /.gitignore: -------------------------------------------------------------------------------- 1 | .DS_Store 2 | target/ 3 | .mooncakes/ 4 | .moonagent/ 5 | -------------------------------------------------------------------------------- /src/stdout.js.mbt: -------------------------------------------------------------------------------- 1 | ///| 2 | extern "js" fn write_internal(s : String) -> Unit = 3 | #|s => process.stdout.write(s) 4 | 5 | ///| 6 | extern "js" fn flush_internal() -> Unit = 7 | #|() => { if (process.stdout.flush) process.stdout.flush(); } 8 | -------------------------------------------------------------------------------- /src/stdout.mbt: -------------------------------------------------------------------------------- 1 | ///| 2 | pub fn[T : Show] write(s : T) -> Unit { 3 | write_internal(s.to_string()) 4 | } 5 | 6 | ///| 7 | pub fn[T : Show] writeln(s : T) -> Unit { 8 | write_internal(s.to_string() + "\n") 9 | } 10 | 11 | ///| 12 | pub fn flush() -> Unit { 13 | flush_internal() 14 | } 15 | -------------------------------------------------------------------------------- /src/stdout_native.c: -------------------------------------------------------------------------------- 1 | #include 2 | #include 3 | 4 | void write_ffi(uint8_t *bytes) 5 | { 6 | if (bytes == NULL) 7 | return; 8 | for (int i = 0; bytes[i] != 0; i++) 9 | putchar(bytes[i]); 10 | } 11 | 12 | void flush_ffi() 13 | { 14 | fflush(stdout); 15 | } -------------------------------------------------------------------------------- /moon.mod.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "oboard/stdout", 3 | "version": "0.1.1", 4 | "deps": { 5 | "moonbitlang/x": "0.4.33" 6 | }, 7 | "readme": "README.md", 8 | "repository": "", 9 | "license": "Apache-2.0", 10 | "keywords": ["stdout", "print", "console"], 11 | "description": "A cross-target stdout library for MoonBit", 12 | "source": "src" 13 | } -------------------------------------------------------------------------------- /src/stdout.native.mbt: -------------------------------------------------------------------------------- 1 | ///| 2 | fn write_internal(s : String) -> Unit { 3 | write_ffi(@encoding.encode(UTF8, s)) 4 | } 5 | 6 | ///| 7 | fn flush_internal() -> Unit { 8 | flush_ffi() 9 | } 10 | 11 | ///| 12 | #owned(bytes) 13 | extern "c" fn write_ffi(bytes : Bytes) -> Unit = "write_ffi" 14 | 15 | ///| 16 | extern "c" fn flush_ffi() -> Unit = "flush_ffi" 17 | -------------------------------------------------------------------------------- /src/moon.pkg.json: -------------------------------------------------------------------------------- 1 | { 2 | "targets": { 3 | "stdout.native.mbt": [ 4 | "native", 5 | "llvm" 6 | ], 7 | "stdout.js.mbt": [ 8 | "js" 9 | ], 10 | "stdout.wasm.mbt": [ 11 | "wasm", 12 | "wasm-gc" 13 | ] 14 | }, 15 | "warn-list": "-1-2-3-6", 16 | "supported-targets": [ 17 | "js", 18 | "native", 19 | "wasm", 20 | "wasm-gc" 21 | ], 22 | "native-stub": [ 23 | "stdout_native.c" 24 | ], 25 | "import": [ 26 | "moonbitlang/x/encoding" 27 | ] 28 | } -------------------------------------------------------------------------------- /src/stdout.wasm.mbt: -------------------------------------------------------------------------------- 1 | // WASM implementation for stdout package 2 | // Uses proper MoonBit FFI syntax for WASM 3 | 4 | // Import print_char function from spectest module (standard for WASM testing) 5 | ///| 6 | fn print_char(c : Int) -> Unit = "spectest" "print_char" 7 | 8 | // Write string by printing each character 9 | 10 | ///| 11 | fn write_internal(s : String) -> Unit { 12 | let len = s.length() 13 | for i = 0; i < len; i = i + 1 { 14 | let char_code = s[i] 15 | print_char(char_code) 16 | } 17 | } 18 | 19 | // Flush is a no-op in basic WASM environment 20 | 21 | ///| 22 | fn flush_internal() -> Unit { 23 | // No flush operation needed for character-by-character output 24 | () 25 | } 26 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # oboard/stdout 2 | 3 | A complete stdout package for MoonBit with cross-platform support (Native C, JavaScript, and WebAssembly). 4 | 5 | ## API Methods 6 | 7 | - `write(s)` - Write content without newline 8 | - `writeln(s)` - Write content with newline 9 | - `print(s)` - Alias for writeln (common convention) 10 | - `flush()` - Force flush output buffer 11 | 12 | ## Usage 13 | 14 | ```moonbit 15 | test { 16 | // Basic writing 17 | write("Hello") 18 | write(", ") 19 | writeln("world!") // Adds newline 20 | } 21 | ``` 22 | 23 | ## Cross-Platform Support 24 | 25 | - **Native (C)**: Uses `putchar()` and `fflush(stdout)` 26 | - **JavaScript**: Uses `process.stdout.write()` and `process.stdout.flush()` 27 | - **WebAssembly**: Basic implementation (requires host environment support for actual output) 28 | 29 | ### WASM Implementation Notes 30 | 31 | The WASM implementation provides a minimal interface that satisfies the API contract. However, actual output functionality depends on the host environment: 32 | 33 | - In a browser environment, you'll need to provide host functions for stdout operations 34 | - In a WASI-compatible runtime, additional WASI bindings would be needed 35 | - The current implementation serves as a foundation that can be extended based on your specific WASM deployment target 36 | -------------------------------------------------------------------------------- /src/README.mbt.md: -------------------------------------------------------------------------------- 1 | # oboard/stdout 2 | 3 | A complete stdout package for MoonBit with cross-platform support (Native C, JavaScript, and WebAssembly). 4 | 5 | ## API Methods 6 | 7 | - `write(s)` - Write content without newline 8 | - `writeln(s)` - Write content with newline 9 | - `print(s)` - Alias for writeln (common convention) 10 | - `flush()` - Force flush output buffer 11 | 12 | ## Usage 13 | 14 | ```moonbit 15 | test { 16 | // Basic writing 17 | write("Hello") 18 | write(", ") 19 | writeln("world!") // Adds newline 20 | } 21 | ``` 22 | 23 | ## Cross-Platform Support 24 | 25 | - **Native (C)**: Uses `putchar()` and `fflush(stdout)` 26 | - **JavaScript**: Uses `process.stdout.write()` and `process.stdout.flush()` 27 | - **WebAssembly**: Basic implementation (requires host environment support for actual output) 28 | 29 | ### WASM Implementation Notes 30 | 31 | The WASM implementation provides a minimal interface that satisfies the API contract. However, actual output functionality depends on the host environment: 32 | 33 | - In a browser environment, you'll need to provide host functions for stdout operations 34 | - In a WASI-compatible runtime, additional WASI bindings would be needed 35 | - The current implementation serves as a foundation that can be extended based on your specific WASM deployment target 36 | -------------------------------------------------------------------------------- /Agents.md: -------------------------------------------------------------------------------- 1 | # Project Agents.md Guide 2 | 3 | This is a [MoonBit](https://docs.moonbitlang.com) project. 4 | 5 | ## Project Structure 6 | 7 | - MoonBit packages are organized per directory, for each directory, there is a 8 | `package.json` file listing its dependencies. Each package has its files and 9 | blackbox test files (common, ending in `_test.mbt`) and whitebox test files 10 | (ending in `_wbtest.mbt`). 11 | 12 | - In the toplevel directory, this is a `moon.mod.json` file listing about the 13 | module and some meta information. 14 | 15 | ## Coding convention 16 | 17 | - MoonBit code is organized in block style, each block is separated by `///|`, 18 | the order of each block is irrelevant. In some refactorings, you can process 19 | block by block independently. 20 | 21 | - Try to keep deprecated blocks in file called `deprecated.mbt` in each 22 | directory. 23 | 24 | ## Tooling 25 | 26 | - `moon fmt` is used to format your code properly. 27 | 28 | - `moon info` is used to update the generated interface of the package, each 29 | package has a generated interface file `.mbti`, it is a brief formal 30 | description of the package. If nothing in `.mbti` changes, this means your 31 | change does not bring the visible changes to the external package users, it is 32 | typically a safe refactoring. 33 | 34 | - In the last step, run `moon info && moon fmt` to update the interface and 35 | format the code. Check the diffs of `.mbti` file to see if the changes are 36 | expected. 37 | 38 | - Run `moon test` to check the test is passed. MoonBit supports snapshot 39 | testing, so when your changes indeed change the behavior of the code, you 40 | should run `moon test --update` to update the snapshot. 41 | 42 | - You can run `moon check` to check the code is linted correctly. 43 | 44 | - When writing tests, you are encouraged to use `inspect` and run 45 | `moon test --update` to update the snapshots, only use assertions like 46 | `assert_eq` when you are in some loops where each snapshot may vary. You can 47 | use `moon coverage analyze > uncovered.log` to see which parts of your code 48 | are not covered by tests. 49 | 50 | - agent-todo.md has some small tasks that are easy for AI to pick up, agent is 51 | welcome to finish the tasks and check the box when you are done 52 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | 2 | Apache License 3 | Version 2.0, January 2004 4 | http://www.apache.org/licenses/ 5 | 6 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 7 | 8 | 1. Definitions. 9 | 10 | "License" shall mean the terms and conditions for use, reproduction, 11 | and distribution as defined by Sections 1 through 9 of this document. 12 | 13 | "Licensor" shall mean the copyright owner or entity authorized by 14 | the copyright owner that is granting the License. 15 | 16 | "Legal Entity" shall mean the union of the acting entity and all 17 | other entities that control, are controlled by, or are under common 18 | control with that entity. For the purposes of this definition, 19 | "control" means (i) the power, direct or indirect, to cause the 20 | direction or management of such entity, whether by contract or 21 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 22 | outstanding shares, or (iii) beneficial ownership of such entity. 23 | 24 | "You" (or "Your") shall mean an individual or Legal Entity 25 | exercising permissions granted by this License. 26 | 27 | "Source" form shall mean the preferred form for making modifications, 28 | including but not limited to software source code, documentation 29 | source, and configuration files. 30 | 31 | "Object" form shall mean any form resulting from mechanical 32 | transformation or translation of a Source form, including but 33 | not limited to compiled object code, generated documentation, 34 | and conversions to other media types. 35 | 36 | "Work" shall mean the work of authorship, whether in Source or 37 | Object form, made available under the License, as indicated by a 38 | copyright notice that is included in or attached to the work 39 | (an example is provided in the Appendix below). 40 | 41 | "Derivative Works" shall mean any work, whether in Source or Object 42 | form, that is based on (or derived from) the Work and for which the 43 | editorial revisions, annotations, elaborations, or other modifications 44 | represent, as a whole, an original work of authorship. For the purposes 45 | of this License, Derivative Works shall not include works that remain 46 | separable from, or merely link (or bind by name) to the interfaces of, 47 | the Work and Derivative Works thereof. 48 | 49 | "Contribution" shall mean any work of authorship, including 50 | the original version of the Work and any modifications or additions 51 | to that Work or Derivative Works thereof, that is intentionally 52 | submitted to Licensor for inclusion in the Work by the copyright owner 53 | or by an individual or Legal Entity authorized to submit on behalf of 54 | the copyright owner. For the purposes of this definition, "submitted" 55 | means any form of electronic, verbal, or written communication sent 56 | to the Licensor or its representatives, including but not limited to 57 | communication on electronic mailing lists, source code control systems, 58 | and issue tracking systems that are managed by, or on behalf of, the 59 | Licensor for the purpose of discussing and improving the Work, but 60 | excluding communication that is conspicuously marked or otherwise 61 | designated in writing by the copyright owner as "Not a Contribution." 62 | 63 | "Contributor" shall mean Licensor and any individual or Legal Entity 64 | on behalf of whom a Contribution has been received by Licensor and 65 | subsequently incorporated within the Work. 66 | 67 | 2. Grant of Copyright License. Subject to the terms and conditions of 68 | this License, each Contributor hereby grants to You a perpetual, 69 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 70 | copyright license to reproduce, prepare Derivative Works of, 71 | publicly display, publicly perform, sublicense, and distribute the 72 | Work and such Derivative Works in Source or Object form. 73 | 74 | 3. Grant of Patent License. Subject to the terms and conditions of 75 | this License, each Contributor hereby grants to You a perpetual, 76 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 77 | (except as stated in this section) patent license to make, have made, 78 | use, offer to sell, sell, import, and otherwise transfer the Work, 79 | where such license applies only to those patent claims licensable 80 | by such Contributor that are necessarily infringed by their 81 | Contribution(s) alone or by combination of their Contribution(s) 82 | with the Work to which such Contribution(s) was submitted. If You 83 | institute patent litigation against any entity (including a 84 | cross-claim or counterclaim in a lawsuit) alleging that the Work 85 | or a Contribution incorporated within the Work constitutes direct 86 | or contributory patent infringement, then any patent licenses 87 | granted to You under this License for that Work shall terminate 88 | as of the date such litigation is filed. 89 | 90 | 4. Redistribution. You may reproduce and distribute copies of the 91 | Work or Derivative Works thereof in any medium, with or without 92 | modifications, and in Source or Object form, provided that You 93 | meet the following conditions: 94 | 95 | (a) You must give any other recipients of the Work or 96 | Derivative Works a copy of this License; and 97 | 98 | (b) You must cause any modified files to carry prominent notices 99 | stating that You changed the files; and 100 | 101 | (c) You must retain, in the Source form of any Derivative Works 102 | that You distribute, all copyright, patent, trademark, and 103 | attribution notices from the Source form of the Work, 104 | excluding those notices that do not pertain to any part of 105 | the Derivative Works; and 106 | 107 | (d) If the Work includes a "NOTICE" text file as part of its 108 | distribution, then any Derivative Works that You distribute must 109 | include a readable copy of the attribution notices contained 110 | within such NOTICE file, excluding those notices that do not 111 | pertain to any part of the Derivative Works, in at least one 112 | of the following places: within a NOTICE text file distributed 113 | as part of the Derivative Works; within the Source form or 114 | documentation, if provided along with the Derivative Works; or, 115 | within a display generated by the Derivative Works, if and 116 | wherever such third-party notices normally appear. The contents 117 | of the NOTICE file are for informational purposes only and 118 | do not modify the License. You may add Your own attribution 119 | notices within Derivative Works that You distribute, alongside 120 | or as an addendum to the NOTICE text from the Work, provided 121 | that such additional attribution notices cannot be construed 122 | as modifying the License. 123 | 124 | You may add Your own copyright statement to Your modifications and 125 | may provide additional or different license terms and conditions 126 | for use, reproduction, or distribution of Your modifications, or 127 | for any such Derivative Works as a whole, provided Your use, 128 | reproduction, and distribution of the Work otherwise complies with 129 | the conditions stated in this License. 130 | 131 | 5. Submission of Contributions. Unless You explicitly state otherwise, 132 | any Contribution intentionally submitted for inclusion in the Work 133 | by You to the Licensor shall be under the terms and conditions of 134 | this License, without any additional terms or conditions. 135 | Notwithstanding the above, nothing herein shall supersede or modify 136 | the terms of any separate license agreement you may have executed 137 | with Licensor regarding such Contributions. 138 | 139 | 6. Trademarks. This License does not grant permission to use the trade 140 | names, trademarks, service marks, or product names of the Licensor, 141 | except as required for reasonable and customary use in describing the 142 | origin of the Work and reproducing the content of the NOTICE file. 143 | 144 | 7. Disclaimer of Warranty. Unless required by applicable law or 145 | agreed to in writing, Licensor provides the Work (and each 146 | Contributor provides its Contributions) on an "AS IS" BASIS, 147 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 148 | implied, including, without limitation, any warranties or conditions 149 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 150 | PARTICULAR PURPOSE. You are solely responsible for determining the 151 | appropriateness of using or redistributing the Work and assume any 152 | risks associated with Your exercise of permissions under this License. 153 | 154 | 8. Limitation of Liability. In no event and under no legal theory, 155 | whether in tort (including negligence), contract, or otherwise, 156 | unless required by applicable law (such as deliberate and grossly 157 | negligent acts) or agreed to in writing, shall any Contributor be 158 | liable to You for damages, including any direct, indirect, special, 159 | incidental, or consequential damages of any character arising as a 160 | result of this License or out of the use or inability to use the 161 | Work (including but not limited to damages for loss of goodwill, 162 | work stoppage, computer failure or malfunction, or any and all 163 | other commercial damages or losses), even if such Contributor 164 | has been advised of the possibility of such damages. 165 | 166 | 9. Accepting Warranty or Additional Liability. While redistributing 167 | the Work or Derivative Works thereof, You may choose to offer, 168 | and charge a fee for, acceptance of support, warranty, indemnity, 169 | or other liability obligations and/or rights consistent with this 170 | License. However, in accepting such obligations, You may act only 171 | on Your own behalf and on Your sole responsibility, not on behalf 172 | of any other Contributor, and only if You agree to indemnify, 173 | defend, and hold each Contributor harmless for any liability 174 | incurred by, or claims asserted against, such Contributor by reason 175 | of your accepting any such warranty or additional liability. 176 | 177 | END OF TERMS AND CONDITIONS 178 | 179 | APPENDIX: How to apply the Apache License to your work. 180 | 181 | To apply the Apache License to your work, attach the following 182 | boilerplate notice, with the fields enclosed by brackets "[]" 183 | replaced with your own identifying information. (Don't include 184 | the brackets!) The text should be enclosed in the appropriate 185 | comment syntax for the file format. We also recommend that a 186 | file or class name and description of purpose be included on the 187 | same "printed page" as the copyright notice for easier 188 | identification within third-party archives. 189 | 190 | Copyright [yyyy] [name of copyright owner] 191 | 192 | Licensed under the Apache License, Version 2.0 (the "License"); 193 | you may not use this file except in compliance with the License. 194 | You may obtain a copy of the License at 195 | 196 | http://www.apache.org/licenses/LICENSE-2.0 197 | 198 | Unless required by applicable law or agreed to in writing, software 199 | distributed under the License is distributed on an "AS IS" BASIS, 200 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 201 | See the License for the specific language governing permissions and 202 | limitations under the License. 203 | --------------------------------------------------------------------------------