Datasets:
Update README.md
Browse files
README.md
CHANGED
@@ -55,4 +55,21 @@ size_categories:
|
|
55 |
---
|
56 |
# Dataset Card for "github-code-haskell-function"
|
57 |
|
58 |
-
[More Information needed](https://github.com/huggingface/datasets/blob/main/CONTRIBUTING.md#how-to-contribute-to-the-dataset-cards)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
55 |
---
|
56 |
# Dataset Card for "github-code-haskell-function"
|
57 |
|
58 |
+
[More Information needed](https://github.com/huggingface/datasets/blob/main/CONTRIBUTING.md#how-to-contribute-to-the-dataset-cards)
|
59 |
+
|
60 |
+
Rows: 3.26M
|
61 |
+
Download Size: 1.17GB
|
62 |
+
|
63 |
+
This dataset is extracted from [github-code-haskell-file](https://huggingface.co/datasets/blastwind/github-code-haskell-file).
|
64 |
+
|
65 |
+
Each row has 3 flavors of the same function:
|
66 |
+
`uncommented_code`: Includes the function and its closest signature.
|
67 |
+
`function_only_code`: Includes the function only.
|
68 |
+
`full_code`: Includes the function and its closest [signature](https://wiki.haskell.org/Type_signature) and comment.
|
69 |
+
The heuristic for finding the closest signature and comment follows: If the immediate previous neighbor of the function
|
70 |
+
is neither a signature nor comment, `full_code` is just the function. If the previous neighbor is one though, include
|
71 |
+
them appropriately, then search the previous neighbor for the other node with the same logic.
|
72 |
+
|
73 |
+
Further, each row also contains attribute values for my personal analysis project. The attributes are calculated from the code in column `uncommented_code`.
|
74 |
+
7% (225k) of the rows have cyclomatic complexity and LOC valued at `-1` because [`homplexity`](https://github.com/BlastWind/homplexity) failed in parsing the row's `uncommented_code`.
|
75 |
+
|