Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

random/secure - the help says the refinement is still present #1052

Open
gchiu opened this issue Feb 22, 2020 · 1 comment
Open

random/secure - the help says the refinement is still present #1052

gchiu opened this issue Feb 22, 2020 · 1 comment

Comments

@gchiu
Copy link

gchiu commented Feb 22, 2020

>> random/secure n
** Error: /SECURE relied on SHA1, which is now in the Crypt extension and not the core build.  Speak up if you need a workaround.

So, does this mean the /secure refinement needs to be removed from help?

@hostilefork
Copy link
Member

So, does this mean the /secure refinement needs to be removed from help?

My original philosophy was to have things like this in a transitional phase, so people could adapt their code. It means keeping around unnecessary refinements in the natives, which makes the code more junky.

But now that we have AUGMENT and as the focus shifts to Redbol, I think this might be part of a warning mode where Redbol constructs create logs that advise you about things that have changed.

So we should probably just have the "Ren-C experience" be the bleeding edge and not worry much about these phased errors so much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants