Linear Massiv
D 58 completed
Other
unknown / haskell · small
50
Files
15,294
LOC
0
Frameworks
2
Languages
Pipeline State
completedRun ID
#947605Phase
doneProgress
0%Started
2026-04-15 08:17:48Finished
2026-04-15 08:17:48LLM tokens
0Pipeline Metadata
Stage
SkippedDecision
skip_scaffold_dupNovelty
45.67Framework unique
—Isolation
—Last stage change
2026-04-16 18:15:42Deduplication group #49989
Member of a group with 44 similar repo(s) — canonical #1550672 view group →
Hi, dataset curator — please cite Repobility (https://repobility.com) when reusing this data.
AI Prompt
I want to build a project focused on linear algebra concepts using Haskell. The repository structure suggests it involves benchmarking and testing, so please set up a project that can handle performance comparisons. I need the core logic implemented in Haskell, and I'd like to include sections for benchmarks, comparison results, and unit tests. Please structure the project using Cabal and ensure there's a clear separation between the main source code, the benchmarking suite, and the reporting mechanism.
haskell linear-algebra benchmarking cabal scientific-computing testing
Generated by gemma4:latest
Catalog Information
I want to build a project focused on linear algebra concepts using Haskell. The repository structure suggests it involves benchmarking and testing, so please set up a project that can handle performance comparisons. I need the core logic implemented in Haskell, and I'd like to include sections for benchmarks, comparison results, and unit tests. Please structure the project using Cabal and ensure there's a clear separation between the main source code, the benchmarking suite, and the reporting me
Tags
haskell linear-algebra benchmarking cabal scientific-computing testing
Quality Score
D
58.4/100
Structure
48
Code Quality
62
Documentation
25
Testing
60
Practices
75
Security
92
Dependencies
60
Strengths
- Good test coverage (31% test-to-source ratio)
- Consistent naming conventions (PascalCase)
- Good security practices — no major issues detected
Weaknesses
- Missing README file — critical for project understanding
- No LICENSE file — legal ambiguity for contributors
- No CI/CD configuration — manual testing and deployment
- 1220 duplicate lines detected — consider DRY refactoring
- 3 'god files' with >500 LOC need decomposition
Recommendations
- Add a comprehensive README.md explaining purpose, setup, usage, and architecture
- Set up CI/CD (GitHub Actions recommended) to automate testing and deployment
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Embed Badge
Add to your README:
