From c6c153261fa801c6cdaa4b7f9f68ff1ff57f1558 Mon Sep 17 00:00:00 2001 From: Ferran Borreguero Date: Fri, 13 Feb 2026 20:08:45 +0800 Subject: [PATCH] Rename repo --- .claude/testing.md | 8 ++++---- Cargo.lock | 2 +- README.md | 4 ++-- benches/Cargo.toml | 2 +- examples/custom-builtin-func/README.md | 2 +- examples/custom-builtin-func/src/main.rs | 2 +- 6 files changed, 10 insertions(+), 10 deletions(-) diff --git a/.claude/testing.md b/.claude/testing.md index c627b73..0ecd1cc 100644 --- a/.claude/testing.md +++ b/.claude/testing.md @@ -1,8 +1,8 @@ -# Testing Guide for PineVM +# Testing Guide for Pinecone ## Overview -Testing is **critical** for PineVM. Every interpreter feature, builtin function, and language construct **MUST** have both positive (success) and negative (error) test cases. +Testing is **critical** for Pinecone. Every interpreter feature, builtin function, and language construct **MUST** have both positive (success) and negative (error) test cases. ## Test Organization @@ -99,7 +99,7 @@ just test-integration-test basic_operations.pine ### For Every Feature -When adding ANY new feature to PineVM, you **MUST** create: +When adding ANY new feature to Pinecone, you **MUST** create: 1. **Positive Test**: Test that the feature works correctly - Test basic functionality @@ -268,4 +268,4 @@ When a test fails: - ✅ One concept per test file - ✅ Clear, descriptive file names and comments -Testing is not optional - it ensures PineVM works correctly and prevents regressions! +Testing is not optional - it ensures Pinecone works correctly and prevents regressions! diff --git a/Cargo.lock b/Cargo.lock index ba358db..ef0a460 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -1438,7 +1438,7 @@ dependencies = [ ] [[package]] -name = "pinevm-benches" +name = "pinecone-benches" version = "0.1.0" dependencies = [ "criterion", diff --git a/README.md b/README.md index 6df0184..4752494 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,8 @@ -# PineVM +# Pinecone A modular PineScript interpreter written in Rust. -PineVM executes PineScript code (TradingView's scripting language) with support for technical analysis, custom indicators, and strategy backtesting. The interpreter is designed to be extensible - you can add custom builtin functions and output types to integrate with your own systems. +Pinecone executes PineScript code (TradingView's scripting language) with support for technical analysis, custom indicators, and strategy backtesting. The interpreter is designed to be extensible - you can add custom builtin functions and output types to integrate with your own systems. ## Features diff --git a/benches/Cargo.toml b/benches/Cargo.toml index 56d3016..5b3a40d 100644 --- a/benches/Cargo.toml +++ b/benches/Cargo.toml @@ -1,5 +1,5 @@ [package] -name = "pinevm-benches" +name = "pinecone-benches" version = "0.1.0" edition = "2021" publish = false diff --git a/examples/custom-builtin-func/README.md b/examples/custom-builtin-func/README.md index 709722f..0be5935 100644 --- a/examples/custom-builtin-func/README.md +++ b/examples/custom-builtin-func/README.md @@ -1,3 +1,3 @@ # Custom Builtin Function Example -This example shows how to extend PineVM with custom output types and builtin functions. +This example shows how to extend Pinecone with custom output types and builtin functions. diff --git a/examples/custom-builtin-func/src/main.rs b/examples/custom-builtin-func/src/main.rs index a686332..f777e64 100644 --- a/examples/custom-builtin-func/src/main.rs +++ b/examples/custom-builtin-func/src/main.rs @@ -1,6 +1,6 @@ /// Example: Custom Builtin Functions with Custom Output /// -/// This example demonstrates how to extend PineVM with: +/// This example demonstrates how to extend Pinecone with: /// 1. A custom output type that stores additional data (alerts) /// 2. A custom builtin function that works with the custom output use pine::Script;