rbcsv 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 584afb981df76a0f55ac321bd65fc0eb6d099e51cd2b95928259f7cb97e66685
+  data.tar.gz: 1df6dde15d314c74efd5559e2a17479957c8fe8ba2de507adae33368a7f8b92f
+SHA512:
+  metadata.gz: d95c37306b9152f1f9a9c23c5d83ca73cef096e37cdbc5fc29fff5a09a3099f7674420f87a427694fc93621443f61dd32d5e9abcba747cbb77adcaaf557362ad
+  data.tar.gz: 226290809496d90809fb03e5a2558770ee021e3750f12ef23eb7efee33fb5e4af1abbb95c7b36ff5cc3301184c0cf87d8276bca4a4f1009a08433a4af365cd45

data/.ruby-version

@@ -0,0 +1 @@
+3.4.5

data/.serena/.gitignore

@@ -0,0 +1 @@
+/cache

data/.serena/memories/code_style_conventions.md

@@ -0,0 +1,27 @@
+# Code Style and Conventions
+
+## Ruby Conventions
+- **Frozen String Literals**: All Ruby files start with `# frozen_string_literal: true`
+- **Module Structure**: Main module is `RCsv` with nested classes/modules
+- **Version Management**: Version is defined in `lib/r_csv/version.rb`
+- **Error Handling**: Custom error class `RCsv::Error < StandardError`
+
+## File Organization
+- **Lib Structure**: Main files in `lib/`, with module-specific files in `lib/r_csv/`
+- **Extension Structure**: Rust code in `ext/r_csv/src/`
+- **Tests**: RSpec tests in `spec/` directory
+
+## Naming Conventions
+- **Gem Name**: `r_csv` (underscore format)
+- **Module Name**: `RCsv` (CamelCase)
+- **File Names**: Snake_case for Ruby files
+- **Constants**: SCREAMING_SNAKE_CASE for version and constants
+
+## Quality Tools
+- **RuboCop**: Used for Ruby style enforcement (configured in `.rubocop.yml`)
+- **RSpec**: Testing framework with configuration in `.rspec`
+
+## Rust Integration
+- **Magnus**: Used for Ruby-Rust bindings
+- **RbSys**: Used for building Ruby extensions with Rust
+- **Extension Path**: Compiled extensions go to `lib/r_csv/`

data/.serena/memories/project_overview.md

@@ -0,0 +1,33 @@
+# R_CSV Project Overview
+
+## Purpose
+R_CSV is a Ruby gem that provides CSV processing functionality using Rust extensions for performance. The gem combines Ruby's ease of use with Rust's performance for CSV operations.
+
+## Tech Stack
+- **Language**: Ruby (>= 3.2.0) with Rust extensions
+- **Build System**: rb_sys for Ruby-Rust integration
+- **Testing**: RSpec
+- **Linting**: RuboCop
+- **Dependencies**: magnus (for Ruby-Rust bindings), rb_sys
+
+## Project Structure
+```
+r_csv/
+├── lib/                    # Ruby source code
+│   ├── r_csv.rb           # Main module file
+│   └── r_csv/
+│       └── version.rb     # Version definition
+├── ext/                   # Rust extension code
+│   └── r_csv/
+│       ├── src/lib.rs     # Rust implementation
+│       ├── Cargo.toml     # Rust dependencies
+│       └── extconf.rb     # Ruby extension configuration
+├── spec/                  # RSpec test files
+├── bin/                   # Executable scripts
+├── r_csv.gemspec         # Gem specification
+├── Rakefile              # Build tasks
+└── Gemfile               # Ruby dependencies
+```
+
+## Current Status
+This appears to be a newly created gem with template code. The Rust extension currently only has a simple "hello" function as a proof of concept.

data/.serena/memories/suggested_commands.md

@@ -0,0 +1,33 @@
+# Suggested Commands for R_CSV Development
+
+## Development Commands
+- `bundle install` - Install dependencies
+- `bin/setup` - Setup the development environment
+- `bin/console` - Start interactive prompt for experimentation
+
+## Build and Compilation
+- `rake compile` - Compile the Rust extension
+- `rake build` - Build the gem (includes compilation)
+- `bundle exec rake install` - Install gem locally
+
+## Testing and Quality
+- `rake spec` - Run RSpec tests
+- `rspec` - Alternative way to run tests
+- `rake rubocop` - Run RuboCop linting
+- `rubocop` - Alternative way to run linting
+- `rake` or `rake default` - Run compile, spec, and rubocop together
+
+## Release
+- `bundle exec rake release` - Release new version (creates git tag, pushes commits and gem)
+
+## Git Commands (macOS/Darwin)
+- `git status` - Check repository status
+- `git add .` - Stage all changes
+- `git commit -m "message"` - Commit changes
+- `git push` - Push to remote repository
+
+## File Operations (macOS/Darwin)
+- `ls` - List directory contents
+- `cd <directory>` - Change directory
+- `grep <pattern> <files>` - Search for patterns
+- `find <path> -name <pattern>` - Find files by name

data/.serena/memories/task_completion_checklist.md

@@ -0,0 +1,29 @@
+# Task Completion Checklist
+
+When completing any development task in r_csv, ensure you run the following commands:
+
+## Required Steps
+1. **Compile Extension**: `rake compile` - Ensure Rust extension compiles without errors
+2. **Run Tests**: `rake spec` - Ensure all tests pass
+3. **Check Code Style**: `rake rubocop` - Ensure code follows style guidelines
+4. **Full Check**: `rake` - Runs compile, spec, and rubocop together
+
+## Before Committing
+- Ensure all tests pass
+- Ensure RuboCop passes without violations
+- Ensure Rust extension compiles successfully
+- Update version number if needed (in `lib/r_csv/version.rb`)
+- Update CHANGELOG.md if applicable
+
+## Release Preparation
+- Update version in `lib/r_csv/version.rb`
+- Update CHANGELOG.md
+- Ensure gemspec is properly configured
+- Run full test suite
+- Check that `bundle exec rake install` works locally
+
+## Git Workflow
+- Use descriptive commit messages
+- Keep commits focused and atomic
+- Test before committing
+- Push to feature branches for review

data/.serena/project.yml

@@ -0,0 +1,67 @@
+# language of the project (csharp, python, rust, java, typescript, go, cpp, or ruby)
+#  * For C, use cpp
+#  * For JavaScript, use typescript
+# Special requirements:
+#  * csharp: Requires the presence of a .sln file in the project folder.
+language: ruby
+
+# whether to use the project's gitignore file to ignore files
+# Added on 2025-04-07
+ignore_all_files_in_gitignore: true
+# list of additional paths to ignore
+# same syntax as gitignore, so you can use * and **
+# Was previously called `ignored_dirs`, please update your config if you are using that.
+# Added (renamed) on 2025-04-07
+ignored_paths: []
+
+# whether the project is in read-only mode
+# If set to true, all editing tools will be disabled and attempts to use them will result in an error
+# Added on 2025-04-18
+read_only: false
+
+# list of tool names to exclude. We recommend not excluding any tools, see the readme for more details.
+# Below is the complete list of tools for convenience.
+# To make sure you have the latest list of tools, and to view their descriptions, 
+# execute `uv run scripts/print_tool_overview.py`.
+#
+#  * `activate_project`: Activates a project by name.
+#  * `check_onboarding_performed`: Checks whether project onboarding was already performed.
+#  * `create_text_file`: Creates/overwrites a file in the project directory.
+#  * `delete_lines`: Deletes a range of lines within a file.
+#  * `delete_memory`: Deletes a memory from Serena's project-specific memory store.
+#  * `execute_shell_command`: Executes a shell command.
+#  * `find_referencing_code_snippets`: Finds code snippets in which the symbol at the given location is referenced.
+#  * `find_referencing_symbols`: Finds symbols that reference the symbol at the given location (optionally filtered by type).
+#  * `find_symbol`: Performs a global (or local) search for symbols with/containing a given name/substring (optionally filtered by type).
+#  * `get_current_config`: Prints the current configuration of the agent, including the active and available projects, tools, contexts, and modes.
+#  * `get_symbols_overview`: Gets an overview of the top-level symbols defined in a given file.
+#  * `initial_instructions`: Gets the initial instructions for the current project.
+#     Should only be used in settings where the system prompt cannot be set,
+#     e.g. in clients you have no control over, like Claude Desktop.
+#  * `insert_after_symbol`: Inserts content after the end of the definition of a given symbol.
+#  * `insert_at_line`: Inserts content at a given line in a file.
+#  * `insert_before_symbol`: Inserts content before the beginning of the definition of a given symbol.
+#  * `list_dir`: Lists files and directories in the given directory (optionally with recursion).
+#  * `list_memories`: Lists memories in Serena's project-specific memory store.
+#  * `onboarding`: Performs onboarding (identifying the project structure and essential tasks, e.g. for testing or building).
+#  * `prepare_for_new_conversation`: Provides instructions for preparing for a new conversation (in order to continue with the necessary context).
+#  * `read_file`: Reads a file within the project directory.
+#  * `read_memory`: Reads the memory with the given name from Serena's project-specific memory store.
+#  * `remove_project`: Removes a project from the Serena configuration.
+#  * `replace_lines`: Replaces a range of lines within a file with new content.
+#  * `replace_symbol_body`: Replaces the full definition of a symbol.
+#  * `restart_language_server`: Restarts the language server, may be necessary when edits not through Serena happen.
+#  * `search_for_pattern`: Performs a search for a pattern in the project.
+#  * `summarize_changes`: Provides instructions for summarizing the changes made to the codebase.
+#  * `switch_modes`: Activates modes by providing a list of their names
+#  * `think_about_collected_information`: Thinking tool for pondering the completeness of collected information.
+#  * `think_about_task_adherence`: Thinking tool for determining whether the agent is still on track with the current task.
+#  * `think_about_whether_you_are_done`: Thinking tool for determining whether the task is truly completed.
+#  * `write_memory`: Writes a named memory (for future reference) to Serena's project-specific memory store.
+excluded_tools: []
+
+# initial prompt for the project. It will always be given to the LLM upon activating the project
+# (contrary to the memories, which are loaded on demand).
+initial_prompt: ""
+
+project_name: "r_csv"

data/CHANGELOG.md

@@ -0,0 +1,6 @@
+## [Unreleased]
+
+## [0.1.0] - 2025-09-20
+
+- Initial release
+## [0.1.0] - 2025-09-20

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official email address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations