# True interactive development

**URL:** <https://discourse.julialang.org/t/true-interactive-development/67318>\
**Category:** Internals & Design\
**Tags:** debugging\
**Created:** [August 30, 2021, 12:38am UTC](https://discourse.julialang.org/t/true-interactive-development/67318 "2021-08-30T00:38:05Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jzr](https://avatars.discourse-cdn.com/v4/letter/j/eb9ed0/32.png) [@jzr](https://discourse.julialang.org/u/jzr)\
**Post date:** [August 31, 2021, 5:25pm UTC](https://discourse.julialang.org/t/true-interactive-development/67318/4 "2021-08-31T17:25:09Z")

</div>

There are a lot of things Revise can’t do currently. Among the most disruptive is the inability to redefine structs.

See also:

> [@Feature request: REPL mode for debugging](https://discourse.julialang.org/t/feature-request-repl-mode-for-debugging/66926):
>
> Wouldn’t it be great to have a REPL mode that’s optimised for debugging rather than ultimate performance? Or maybe it has some experimental features that can be turned on at the user’s own risk? Some features that might be useful when debugging at the cost of some potential performance loss: Avoid optimising IO code for faster printing Method selection and type inference while the user is typing the commands! For example if I am typing println(x) and x is a vector of floats, before typing ) an…

---

_[View the full topic](https://discourse.julialang.org/t/true-interactive-development/67318)._