Skip to content

Commit 177d61f

Browse files
trcrsiredtrcrsired
committed
Deal with several mistakes in documentaions for the usage of copilot
1 parent 4f57941 commit 177d61f

3 files changed

Lines changed: 214 additions & 215 deletions

File tree

‎docs/docs/01.helloworld/index.html‎

Lines changed: 49 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -1,49 +1,49 @@
1-
<!DOCTYPE html>
2-
<html lang="en">
3-
<head>
4-
<meta charset="UTF-8">
5-
<meta name="viewport" content="width=device-width, initial-scale=1.0">
6-
<title>Hello World - fast_io Documentation</title>
7-
<link rel="stylesheet" href="/style.css">
8-
<link rel="manifest" href="/manifest.json">
9-
</head>
10-
<body>
11-
<main>
12-
<h1>Hello World</h1>
13-
14-
<section>
15-
<h2>Hello World</h2>
16-
<p>
17-
A minimal program using <code>fast_io</code> to print <em>Hello World</em>:
18-
</p>
19-
<pre><code class="language-cpp">
20-
#include &lt;fast_io.h&gt;
21-
22-
int main()
23-
{
24-
using namespace ::fast_io::io;
25-
print("Hello World\n");
26-
}
27-
</code></pre>
28-
<p>
29-
By default, <code>fast_io::print</code> writes to C’s <code>FILE*</code> <code>stdout</code> object.
30-
This means the output goes to the standard output stream, just like <code>printf</code> or
31-
<code>std::cout</code>, but with safer and faster semantics.
32-
</p>
33-
<p>
34-
In practice, using <code>fast_io</code> together with <code>stdio</code> or <code>iostream</code>
35-
usually does not cause issues. The only problematic cases arise if code calls unusual functions
36-
like <code>unput</code>, which can break assumptions because neither <code>stdio</code> nor
37-
<code>iostream</code> guarantee consistent behavior for such operations. As long as you avoid
38-
those unsafe edge cases, interoperability is fine.
39-
</p>
40-
</section>
41-
42-
<div class="page-navigation">
43-
<a href="/docs/intro" class="prev-button">← Previous: Introduction</a>
44-
<a href="/" class="main-button">↑ Back to Main Page</a>
45-
<a href="/docs/02.aplusb" class="next-button">Next: A + B Example →</a>
46-
</div>
47-
</main>
48-
</body>
49-
</html>
1+
<!DOCTYPE html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="UTF-8">
5+
<meta name="viewport" content="width=device-width, initial-scale=1.0">
6+
<title>Hello World - fast_io Documentation</title>
7+
<link rel="stylesheet" href="/style.css">
8+
<link rel="manifest" href="/manifest.json">
9+
</head>
10+
<body>
11+
<main>
12+
<h1>Hello World</h1>
13+
14+
<section>
15+
<h2>Hello World</h2>
16+
<p>
17+
A minimal program using <code>fast_io</code> to print <em>Hello World</em>:
18+
</p>
19+
<pre><code class="language-cpp">
20+
#include &lt;fast_io.h&gt;
21+
22+
int main()
23+
{
24+
using namespace ::fast_io::io;
25+
print("Hello World\n");
26+
}
27+
</code></pre>
28+
<p>
29+
By default, <code>::fast_io::io::print</code> writes to C’s <code>FILE*</code> <code>stdout</code> object.
30+
This means the output goes to the standard output stream, just like <code>printf</code> or
31+
<code>std::cout</code>, but with safer and faster semantics.
32+
</p>
33+
<p>
34+
In practice, using <code>fast_io</code> together with <code>stdio</code> or <code>iostream</code>
35+
usually does not cause issues. The only problematic cases arise if code calls unusual functions
36+
like <code>unput</code>, which can break assumptions because neither <code>stdio</code> nor
37+
<code>iostream</code> guarantee consistent behavior for such operations. As long as you avoid
38+
those unsafe edge cases, interoperability is fine.
39+
</p>
40+
</section>
41+
42+
<div class="page-navigation">
43+
<a href="/docs/intro" class="prev-button">← Previous: Introduction</a>
44+
<a href="/" class="main-button">↑ Back to Main Page</a>
45+
<a href="/docs/02.aplusb" class="next-button">Next: A + B Example →</a>
46+
</div>
47+
</main>
48+
</body>
49+
</html>

0 commit comments

Comments
 (0)