<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>src/libstd/os/raw/ulong.md - fork/rust @ 1.43.1</title>
<meta name="description" content="src/libstd/os/raw/ulong.md in fork/rust at 1.43.1.">
<meta property="og:title" content="src/libstd/os/raw/ulong.md - fork/rust @ 1.43.1">
<meta property="og:description" content="src/libstd/os/raw/ulong.md in fork/rust at 1.43.1.">
<meta property="og:type" content="website">
<meta property="og:site_name" content="git.julia.blue">
<link rel="stylesheet" href="/css/style.css?v=62">
<script type="module" src="/js/main.js?v=62"></script>
</head>
<body>
<main data-ref="1.43.1" data-tip="8d69840ab92ea7f4d323420088dd8c9775f180cd">
<noscript>
  <div class="callout">
    <p>
      hey! this is a static git repo viewer. commit diffs, file history,
      older commits and other revisions won't load without javascript.
    </p>
    <p>
      you are still able to view source files on branch/tag tips,
      but the experience is degraded.
    </p>
  </div>
</noscript>
<header class="repo"><div>
<h1>fork/rust</h1>
</div>
<pre class="clone">git clone https://git.julia.blue/fork/rust</pre>
</header>
<p class="snapshot-commit"><span class="commit-author">bors</span><span class="commit-message" data-commit="8d69840ab92ea7f4d323420088dd8c9775f180cd">Auto merge of #71868 - Mark-Simulacrum:stable-1.43.1, r=pietroalbini</span><span class="snapshot-sha sha" data-commit="8d69840ab92ea7f4d323420088dd8c9775f180cd">8d69840ab92</span><time datetime="2020-05-04T23:45:41+00:00" title="2020-05-04 23:45:41 +0000">2020-05-04</time></p>
<header class="topbar"><details class="switcher"><summary>1.43.1</summary><div class="menu"><strong>branches</strong><a href="/fork/rust/ref/master/">master</a><strong>tags</strong><a href="/fork/rust/ref/1.39.0/">1.39.0</a><a href="/fork/rust/ref/1.40.0/">1.40.0</a><a href="/fork/rust/ref/1.41.0/">1.41.0</a><a href="/fork/rust/ref/1.41.1/">1.41.1</a><a href="/fork/rust/ref/1.42.0/">1.42.0</a><a href="/fork/rust/ref/1.43.0/">1.43.0</a><a class="current" href="/fork/rust/ref/1.43.1/">1.43.1</a><a href="/fork/rust/ref/1.44.0/">1.44.0</a><a class="all" href="/fork/rust/refs">all refs →</a></div></details><nav class="crumbs"><a href="/fork/rust/">rust</a> / <a href="/fork/rust/ref/1.43.1/tree/src/">src</a> / <a href="/fork/rust/ref/1.43.1/tree/src/libstd/">libstd</a> / <a href="/fork/rust/ref/1.43.1/tree/src/libstd/os/">os</a> / <a href="/fork/rust/ref/1.43.1/tree/src/libstd/os/raw/">raw</a> / <span class="cur">ulong.md</span></nav>
<span class="view-stats"><span>461 B</span><span>7 lines</span></span><span class="actions"><a class="raw" href="/fork/rust/raw/c350395080e80f429aa1ec71b42235ef9be87b64/src/libstd/os/raw/ulong.md">raw</a></span></header>
<div class="markdown-view"><input type="radio" name="markdown-view" id="markdown-rendered" checked><label for="markdown-rendered">rendered</label><input type="radio" name="markdown-view" id="markdown-code"><label for="markdown-code">code</label><section class="readme rendered"><p>Equivalent to C's <code>unsigned long</code> type.</p>
<p>This type will always be <a href="../../primitive.u32.html"><code>u32</code></a> or <a href="../../primitive.u64.html"><code>u64</code></a>. Most notably, many Linux-based systems assume an <code>u64</code>, but Windows assumes <code>u32</code>. The C standard technically only requires that this type be an unsigned integer with the size of a <a href="type.c_long.html"><code>long</code></a>, although in practice, no system would have a <code>ulong</code> that is neither a <code>u32</code> nor <code>u64</code>.</p>
</section><div class="code-panel"><pre class="code src" data-hl="src/libstd/os/raw/ulong.md"><span class="code-line"><a class="ln" id="L1" href="#L1">1</a><span class="code-text">Equivalent to C's `unsigned long` type.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L2" href="#L2">2</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L3" href="#L3">3</a><span class="code-text">This type will always be [`u32`] or [`u64`]. Most notably, many Linux-based systems assume an `u64`, but Windows assumes `u32`. The C standard technically only requires that this type be an unsigned integer with the size of a [`long`], although in practice, no system would have a `ulong` that is neither a `u32` nor `u64`.</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L4" href="#L4">4</a><span class="code-text"></span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L5" href="#L5">5</a><span class="code-text">[`long`]: type.c_long.html</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L6" href="#L6">6</a><span class="code-text">[`u32`]: ../../primitive.u32.html</span><span class="code-break">
</span></span><span class="code-line"><a class="ln" id="L7" href="#L7">7</a><span class="code-text">[`u64`]: ../../primitive.u64.html</span></span></pre></div></div>
</main>
</body>
</html>
