-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please, put the to/fromList conversion cost more clearly #101
Comments
You elided the important part: “Repeated uses of I'm not sure what you mean by “ad hominem” here, but I don't think I'm guilty of committing an informal logical fallacy. There may be room for improvement on the documentation, but it seems you figured out what it meant, which is the important thing. Thanks for your interest! But I think it's good enough for now. |
For me - using informal Sometimes after Sometimes the side-effect of informal |
I do mention, that theme does not involve the value of But I do think that lack of documentation on |
Currently the main info is in
fromList
dlist/Data/DList/Internal.hs
Lines 104 to 136 in 1793a5e
This paragraph:
"If you find yourself doing some form of the following" implies that everything that follows - is counterproductive. & logically both
fromList . f . toList
&toList . g . fromList
for simple things are counterproductive. & "following" statement opens - and never stops, never says where examples & "following" stops & it does not even have a.
at the end of sentences - so that means "everything that follows"."If you find yourself doing some form of the following ... More likely, you will convert ..." - what does that mean = it is an ad hominem probabilistic characteristic, not a statement or explanation, moreover it applies things to me and not to a library or compiler. It not forgot to mention me in the docs, but forgot to mention if the way discussed there is recommended, or as "following" implies - just as counterproductive. Dwelling on ad hominems
you
we
so much - to show a trend in the documentation of use those easy escape words as diversions, instead of the description of the process & objects involved. If to just remove personal directioning from docs - they suddenly both shorter & understandable.As:
suddenly text 2 times shorter & clear.
Moreover - that paragraph can be removed entirely as tautology - of course doing operations with other type & functions - is not using
DList
.Having
O
notation & statingfrom/toList
costs is enough to infer where it is useful.I vaguely remember reading about
DList
directions of conversion, but it was years ago & do not remember if anisotropy (directional properties) came out being imaginary or real, if it is stated clearly in the doc - users would not need to remember it from years ago & would not get puzzled.The text was updated successfully, but these errors were encountered: