From f57a2c1e85387afe48b7bdb57176dafb156bb86e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bartek=20Iwa=C5=84czuk?= Date: Sun, 6 Sep 2020 21:44:29 +0200 Subject: refactor(core): rename CoreIsolate to JsRuntime (#7373) deno_core/ - rename core_isolate.rs to runtime.rs - rename CoreIsolate to JsRuntime - rename JSError to JsError - rename JSStackFrame to JsStackFrame cli/ - update references from deno_core::CoreIsolate to deno_core::JsRuntime - rename deno_core::JSError to deno_core::JsError - rename fmt_errors::JSError to fmt_errors::JsError --- cli/errors.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'cli/errors.rs') diff --git a/cli/errors.rs b/cli/errors.rs index 327bcfb58..ffa0b95e4 100644 --- a/cli/errors.rs +++ b/cli/errors.rs @@ -3,11 +3,11 @@ //! There are many types of errors in Deno: //! - ErrBox: a generic boxed object. This is the super type of all //! errors handled in Rust. -//! - JSError: a container for the error message and stack trace for exceptions +//! - JsError: a container for the error message and stack trace for exceptions //! thrown in JavaScript code. We use this to pretty-print stack traces. //! - Diagnostic: these are errors that originate in TypeScript's compiler. -//! They're similar to JSError, in that they have line numbers. -//! But Diagnostics are compile-time type errors, whereas JSErrors are runtime +//! They're similar to JsError, in that they have line numbers. +//! But Diagnostics are compile-time type errors, whereas JsErrors are runtime //! exceptions. use crate::import_map::ImportMapError; -- cgit v1.2.3