-
Notifications
You must be signed in to change notification settings - Fork 7
/
Copy pathindex.html
106 lines (93 loc) · 5.37 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
<!DOCTYPE html>
<!--[if IE]><![endif]-->
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>LibLangly Documentation </title>
<meta name="viewport" content="width=device-width">
<meta name="title" content="LibLangly Documentation ">
<meta name="generator" content="docfx 2.58.9.0">
<link rel="shortcut icon" href="favicon.ico">
<link rel="stylesheet" href="styles/docfx.vendor.css">
<link rel="stylesheet" href="styles/docfx.css">
<link rel="stylesheet" href="styles/main.css">
<meta property="docfx:navrel" content="toc.html">
<meta property="docfx:tocrel" content="toc.html">
</head>
<body data-spy="scroll" data-target="#affix" data-offset="120">
<div id="wrapper">
<header>
<nav id="autocollapse" class="navbar navbar-inverse ng-scope" role="navigation">
<div class="container">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#navbar">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="index.html">
<img id="logo" class="svg" src="logo.svg" alt="">
</a>
</div>
<div class="collapse navbar-collapse" id="navbar">
<form class="navbar-form navbar-right" role="search" id="search">
<div class="form-group">
<input type="text" class="form-control" id="search-query" placeholder="Search" autocomplete="off">
</div>
</form>
</div>
</div>
</nav>
<div class="subnav navbar navbar-default">
<div class="container hide-when-search" id="breadcrumb">
<ul class="breadcrumb">
<li></li>
</ul>
</div>
</div>
</header>
<div role="main" class="container body-content hide-when-search">
<div class="article row grid">
<div class="col-md-10">
<article class="content wrap" id="_content" data-uid="">
<h1 id="liblangly-documentation">LibLangly Documentation</h1>
<p>This is the combined documentation for all parts of <strong>LibLangly</strong>. If you're looking for the docs for <strong>Stringier</strong>, <strong>Collectathon</strong>, or other components that had their own discrete documentation before, that's all been merged together here.</p>
<h2 id="articles-or-api-docs">Articles or API docs?</h2>
<p>Articles are generally broken down by concept, rather than specific bit of code. This is done because all code units are documented, and that documentation is always up to date with the most recent repo contents. That documentation, especially in the <code><remarks></code> section, discusses any technical details about that specific unit. Instead, it makes more sense for the articles to discuss the high level stuff. Why are the collections designed the way they are and how do you pick which one to use? That is article content.</p>
<h2 id="cross-language">Cross Language</h2>
<p><strong>LibLangly</strong> has been designed with cross-language use in mind. There are some caveats however. C# and F# consumers should largely be fine. C# directly, and F# through the use of language bindings to provide a function/pipeline-first experience. VisualBasic.NET has been abandoned by Microsoft in everything except a formal statement. Many parts of these libraries are still usable from VB, but anything requiring heavy use of references, which is the overwhelming majority of <strong>Collectathon</strong>, as well as many parts of <strong>Stringier</strong> and <strong>Philosoft</strong> are going to regularly run into problems. Other CLS Consumers such as RemObjects' <a href="https://www.elementscompiler.com/elements/mercury/">Mercury</a>, a VB "clone", but really more of a successor, <em>should</em> work well regardless. However, I do not have a license for RemObjects' <a href="https://www.elementscompiler.com/elements/default.aspx">Elements</a>, and therefore am unable to personally verify this.</p>
</article>
</div>
<div class="hidden-sm col-md-2" role="complementary">
<div class="sideaffix">
<div class="contribution">
<ul class="nav">
</ul>
</div>
<nav class="bs-docs-sidebar hidden-print hidden-xs hidden-sm affix" id="affix">
<h5>In This Article</h5>
<div></div>
</nav>
</div>
</div>
</div>
</div>
<footer>
<div class="grad-bottom"></div>
<div class="footer">
<div class="container">
<span class="pull-right">
<a href="#top">Back to top</a>
</span>
<span>Generated by <strong>DocFX</strong></span>
</div>
</div>
</footer>
</div>
<script type="text/javascript" src="styles/docfx.vendor.js"></script>
<script type="text/javascript" src="styles/docfx.js"></script>
<script type="text/javascript" src="styles/main.js"></script>
</body>
</html>