Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Arti
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jill
Arti
Commits
36314ad3
Commit
36314ad3
authored
3 years ago
by
Nick Mathewson
Browse files
Options
Downloads
Patches
Plain Diff
tor_error: a couple of spelling/formatting issues
parent
990753ca
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
crates/tor-error/src/lib.rs
+4
-4
4 additions, 4 deletions
crates/tor-error/src/lib.rs
with
4 additions
and
4 deletions
crates/tor-error/src/lib.rs
+
4
−
4
View file @
36314ad3
...
...
@@ -211,7 +211,7 @@ pub enum ErrorKind {
/// may indicate that you're using something that isn't implemented yet.
///
/// This kind can relate both to operations which we plan to implement, and
/// to operations which we do not. It does not relate to faciities which
/// to operations which we do not. It does not relate to faci
l
ities which
/// are disabled (e.g. at build time) or harmful.
///
/// It can refer to facilities which were once implemented in Tor or Arti
...
...
@@ -220,10 +220,10 @@ pub enum ErrorKind {
NotImplemented
,
/// A feature was requested which has been disabled in this build of Arti.
///
!
/// This kind of error happens when the running Arti was built wit
y
out the
///
/// This kind of error happens when the running Arti was built wit
h
out the
/// appropriate feature (usually, cargo feature) enabled.
///
!
///
/// This might indicate that the overall running system has been
/// mis-configured at build-time. Alternatively, it can occur if the
/// running system is deliberately stripped down, in which case it might be
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment