Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
GHC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Alexander Kaznacheev
GHC
Commits
b70f6119
Commit
b70f6119
authored
14 years ago
by
David Terei
Committed by
Ian Lynagh
14 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Fix typo in Safe Haskell doc
parent
1e10605c
Loading
Loading
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/users_guide/safe_haskell.xml
+1
-1
1 addition, 1 deletion
docs/users_guide/safe_haskell.xml
with
1 addition
and
1 deletion
docs/users_guide/safe_haskell.xml
+
1
−
1
View file @
b70f6119
...
...
@@ -43,7 +43,7 @@
<listitem><emphasis>
Module boundary control.
</emphasis>
Haskell code
compiled using the Safe language is guaranteed to only access
symbols that are publicly available to it through other modules
export lists. An import part of this is that safe compiled code
export lists. An import
ant
part of this is that safe compiled code
is not able to examine or create data values using data constructors
that the module cannot import. If a module M establishes some
invariants through careful use of its export list then code
...
...
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