text:
Salmons Brook Flood Alleviation Works Planning Panel, Planning Panel - Monday, 9th July, 2012 7.00 pm
Agenda reports pack PDF 62 KB
Printed draft minutes PDF 58 KB
Venue: Highlands Secondary School, 148 Worlds End Lane, London, N21 1QQ
Contact: Jane Creer 020 8379 4093 Email: jane.creer@enfield.gov.uk
(i) Purpose of the meeting
(ii) Introduction of Applicant's representatives and Officers of the Council.
1. Councillor Delman as Chairman welcomed all attendees to the meeting and introduced the Panel Members, the applicant's representatives and Council officers.
2. The purpose of the meeting was to provide local residents and other interested parties the opportunity to ask questions about the application and for the applicants, officers and Panel Members to listen to all the comments.
3. A decision on the application would be made by the full Planning Committee at a future date.
OFFICERS' SUMMARY OF THE PLANNING ISSUES
This application concerns the entire course of Salmons Brook, which runs through the Borough from its source at Enfield Chase, to its confluence with Pymmes Brook (and thence the River Lea), on the south side of the North Circular Road. Residential properties and businesses have been the subject of flooding from Salmons Brook on a number of occasions, causing disruption and material damage to property. This scheme would alleviate the flooding by proposing the following physical work at three locations along the course of the Brook:
1 Enfield Golf Course, along its southern boundary with the Cheyne Walk Open Space and Allotments, and to the north-east of residential properties in Grange Park, N21.
2 Montagu Road, Edmonton,
(i) along part of Salmons Brook Walk, between Plevna Road and Montagu Road,
(ii) through part of the Montagu Recreation Ground,
(iii) along part of Cemetery Walk, (to the south of the cemetery).
3 Bury Street West, this will involve river improvement works at Bury Lodge but this is for environmental benefit not for flood risk reduction.
The proposals include a combination of flood storage and improved water-conveyance. Flood waters would be stored upstream at Enfield Golf Course through the creation of a grassed embankment across Salmons Brook to allow more flood water to be stored temporarily on the existing floodplain during flood events, reducing flows downstream. The embankment and area for temporary storage of water at the Golf Course will occupy approximately 15.6 hectares, mostly on the Golf Course but partly on the Cheyne Walk Open Space.
The scheme also includes raised riverside flood defences (low walls and embankments) along Salmons Brook between Plevna Road and Montagu Road that will reduce the frequency the brook bursts its banks in this location. Additional improvements to the culvert would also take place under Montagu Road to reduce the risk of blockages to the Brook and the Recreation Ground will have a new grassed embankment so that it can temporarily store more water on the existing floodplain (as at the Golf Course). The combined area of the Salmons Walk and Montagu Recreation Ground sites is approximately 8.5 hectares.
The proposed scheme would involve sustained period of construction works lasting up to 12 months at the Golf Course and 18 months at locations around Salmons Walk and Montagu Recreation Ground. Haulage routes would utilise local road networks are the main routes are summarised as follows:
Enfield Golf Course: A110 westbound through Enfield Town Centre, turning south onto Bincote Road, then along Worlds End Lane, Green Dragon Lane. Cadogan Gardens and Vera Avenue, to access the site via Uplands Way;
Salmons Walk: North Circular Road then A1010 Fore Street turning right into Plevna Road to site;
Montagu Recreation Ground and the eastern end of Salmons Walk: A406(T) North Circular eastbound then B137 (Montagu Road) to site.
Bury Lodge via the adjacent A10 turning into Bury Street West ... view the full agenda text for item 2.
1. Aled Richards, Head of Development Management, advised that a printed summary of the proposals had been left on each chair.
2. The application had been submitted over a month ago. Over 1200 local properties had been consulted directly, mainly along the construction traffic routes and adjoining the sites. The plan provided showed the extent of the consultation letters sent. Notices had also been put up on sites. To date, 30 letters of objection had been received.
3. Comments made at this meeting would be noted, and the Environment Agency would also be working on further consultation.
4. Most of the concerns raised so far related to pedestrian access to sites, noise and disturbance, potential damage from construction vehicles and loss of use of Enfield Golf Course and Cheyne Walk Open Space.
5. Comments received from statutory consultees so far were summarised:
? Ecology officers had raised concerns in respect of the biodiversity assessment which dated from 2008, and had requested another survey. This would have to be carried out between July and September so would affect the progress of the application which would not be able to be presented to Planning Committee until October at the earliest.
? The Conservation Advisory Group had no objections and felt that the merits of the scheme outweighed any adverse impacts on Conservation Areas.
? The Friends of Bury Lodge Park had raised concerns about implications for children's safety and wildlife.
? Grange Park Residents' Association had raised concerns about site noise, emissions, HGV movements, and site access.
? Highlands School had raised concerns about levels and routes of site traffic and the health and safety of pedestrians walking to school.
? McMullen brewers had raised concerns around the Jolly Farmers pub site.
? Thames Water had raised no objections, but required additional information in relation to Deephams sewage works.
? Transport for London had no objections.
? National Grid Electricity Network had no objections.
? Western Enfield Residents' Association had raised concerns about flood risk to properties and damage to roads in its area.
6. The main planning implications to be considered were traffic issues, access to sites during construction, extent and duration of construction works, construction noise and disturbance to neighbouring amenity, and flood risk to properties adjoining the flood storage areas.
7. Updated plans were displayed at the rear of the hall.
8. The consultation period finished on 23 July, but Enfield Council took a pragmatic approach and would welcome written comments right up to the date of the Planning Committee, which was likely to be in late October.
PRESENTATION BY THE APPLICANT / AGENT
1. Steve Whipp, Senior User – Client, Environment Agency, introduced the project members present and gave an illustrated presentation on the proposal, including:
a. In 2000 there was severe flooding in Edmonton when 192 properties were flooded internally and some people were not able to return to their homes for over a year. This was a quite rare event, but the impact was severe.
b. The objectives of the scheme were a significant improvement to flooding risk, improvements to the environment, and achievement of a benefit – cost ratio of over 6. Maps were available of the benefit areas.
c. The main elements of the scheme were described:
? Enfield Golf Course would be used for temporary storage of flood water. For the vast majority of the time the course would be unaffected. The design was environmentally sensitive to minimise loss of trees. The structure would be safe to operate and be as simple as possible. The routes over the embankment would also tie in with the greenway path. There would be no change in flood risk upstream of the golf course.
? The aim in the Montagu Road area was to stop water going into houses and through the cemeteries. A new culvert would smooth the flow. Water would be contained at Montagu Road Recreation Ground.
? Artist's impressions had been produced of how sites would look after the scheme.
d. Proposed routes for construction access to the sites were set out. Concerns were acknowledged about the route to Enfield Golf Course and vehicles would avoid peak times and school arrival and leaving times. Salmons Walk only had entrances from Plevna Road and Montagu Road; a compound would be established on the recreation ground. At Bury Street West there would be fairly minimal works for about 3 weeks, accessed through the existing Council depot.
e. Access to the public had been taken into account at all sites.
? The full 18 holes would be playable at Enfield Golf Course with a temporary tee at a slightly shortened 9th hole.
? At Cheyne Walk there would be pedestrian access at all times to the allotments and open space with a segregated pedestrian route so people would be safe, and vehicular access at evenings and weekends and in special circumstances by arrangement.
? At Barnabas Court there would be pedestrian and vehicular access to the sheltered housing at all times and there would be a vehicle marshall on that entrance.
? Salmons Walk was a constrained site and to protect members of the public access could not be allowed during the works, but an alternative route would be signed, and post scheme there would be improvements.
? At Montagu Road, access to current play areas, community centre and sports field would be maintained during the works and the minimum space possible would be occupied on the recreation ground. Temporary traffic lights would be required while the culvert was constructed on the edge of Montagu Road.
? The site at Bury Street West was currently closed to ... view the full minutes text for item 3.
QUESTIONS BY PANEL MEMBERS
NOTED the following questions and observations from Members of the Panel:
1. Councillor Delman asked about the possibilities of diverting water from Salmons Brook to the New River or Pymmes Brook earlier to remove the need to store water; or if there must be water storage could it be held elsewhere? It was advised that potential diversion culverts had been considered, but were very expensive because of their length and not practical. Use of the New River also risked contamination of the water supply. If Pymmes Brook and Salmons Brook were running full, the New River as a man-made channel had a limited capacity to accept flood water. The same applied for Sadlers Mill Stream. The main policy document for all flood alleviation schemes was called 'Making Space for Water' and the aim was for storage and attenuation on a natural flood plain.
2. Councillor Constantinides mentioned the positive suggestions made during consultation, especially by Enfield Golf Club members and asked whether any ideas had been taken up. He also asked about the overall project timing. It was confirmed that there had been previous consultation and exhibitions and it had been tried as far as practicable to incorporate previous consultations. The first part of the project to be finished would be Enfield Golf Course, then Montagu Recreation Ground and finally Salmons Walk.
3. In response to Councillor Hurer's queries, it was advised that normal working hours defined as acceptable were 8:00am to 6.00pm and that construction hours would be written into the contract and would be agreed with the Local Authority. HGV movements would be avoided at school hours. Discussions had been held with the Golf Club regarding alleviation of more frequent flooding and making the course more playable than at the moment post scheme. In an extreme event the intention was to inundate the golf course to protect other areas.
4. Councillor Ekechi asked about minimisation of disturbance and noise and the hours of construction work. It was advised that early in the morning and late in the evening, contractors would be just setting up and finishing. While work was progressing there would be liaison with local communities and collection of feedback. There were statutory limits on noise and vibration. There would also be a Section 106 Agreement with further constraints which the applicant would be bound by.
5. In response to Councillor Keazor's queries regarding the total timescale for the scheme, it was confirmed that the works at Enfield Golf Club would be likely to take just over a year, and works at Salmons Walk and Montagu Road around one and a half years. There were two sets of allotments near the scheme. A beneficial side effect would be that allotments at Cheyne Walk would flood less frequently and at Salmons Walk the allotments would receive protection from the wall along Salmons Walk.
QUESTIONS BY WARD COUNCILLORS
NOTED the following questions and observations from Ward Councillors:
1. Councillor Glynis Vince, Grange Ward Councillor, questioned whether any benefits would be brought to Grange and Highlands wards. On 9 and 11 June there had been flooding in parts of those wards, especially at the golf course / Cheyne Walk / Slades Rise areas, but not in Edmonton.
It was advised that the recent flooding had a chance of occurring at any time from river water escaping when the water was high, but there were no homes in that flood plain. In Edmonton, flooding to people's homes could be expected in 1 in 20 years. The consequences on open spaces were a lot less: within days they could be used again and there was no permanent impact. The whole scheme would cost just over £15 million.
Councillor Vince understood there could be 40 traffic movements a day, and 54,000 tonnes of clay to be moved, and she asked whether the condition of residential properties had been surveyed.
It was advised that the busiest time during construction would be when bringing in materials for the embankment when there would be up to 40 vehicle movements a day in total in and out. Outside that busy period there would be a lot less movements. 54,000 tonnes of clay was the total for the whole project, and the golf club site would involve about half that amount. Potential for property damage was very low risk: previous experience in Uxbridge had shown that such traffic did not cause structural damage. Surveys were proposed just before the start of construction, so were not done yet.
Councillor Vince remained concerned that the roads involved in this project were narrower, and that even outside school run times, Worlds End Lane and Bincote Road had a constant flow of traffic.
2. Councillor Jon Kaye, Highlands Ward Councillor, highlighted that flooding occurred often 3 or 4 times a year in the Links Side / Slades Rise / Taunton Drive vicinity. He considered that the residents in these roads would not be helped and any flood alleviation scheme should be more comprehensive.
It was advised that there could be multiple sources of flooding, including from drains and roads, not just from the river running full. In low frequency events this scheme would alleviate flooding to these properties. This scheme was designed to mitigate against a single event such as happened in 2000. In such an event the works at the golf club would deal with the flow more quickly.
3. Councillor Neville, Grange Ward Councillor, questioned the proven need for the scheme at this time. There had been major repair costs after the event in 2000, and work done then may have contributed to flooding not recurring in the years that followed or during recent rainfall.
It was advised that in an event on the scale of that in 2000, flooding would still have occurred without a larger scheme in place. Comparison should be made with a situation similar ... view the full minutes text for item 5.
OPEN SESSION - QUESTIONS AND VIEWS FROM THE FLOOR
NOTED the following comments and questions were received from local residents and other interested parties:
1. The headteacher of Highlands School clarified that an objection had been raised by Highlands, Merryhills and Grange Park schools combined in respect of the volume of traffic, and about the quality of the documentation as there was no summary of the project in clear language and no easily-understandable map. He questioned why the vehicle route from the A10 had to approach Green Dragon Lane via Bincote Road and Worlds End Lane, passing three schools. Highlands School in particular had students in the sixth form who came and went throughout the day. He considered that temporary changes to traffic islands in Green Lanes would be a cost worth bearing to avoid these schools. These roads were difficult to negotiate at the quietest times and heavy lorries would cause chaos.
It was advised that the traffic routes had been carefully considered and the route chosen was the best, least-intrusive option. On busier roads, the increase in traffic would be less obvious.
2. Other residents also expressed their concern about the large numbers of children who used the local roads to go to and from school and the heavy lorry use of those roads.
3. In response to a resident's queries about potential alternatives including a reservoir elsewhere, it was advised that it was best to store flood water as close as possible to the area to be benefited. Between this location and Edmonton, there were very few green spaces, and they had other uses, and the best choice was this natural flood plain.
4. A resident raised particular concerns about the current condition of Cadogan Gardens roadway and likely severe damage resulting from construction vehicles, and that heavy lorries would exacerbate the frequent flooding experienced due to broken water pipes in Worlds End Lane, Green Dragon Lane and Eversley Park Road.
5. The Enfield Golf Club Chairman considered that the scheme would jeopardise the survival of the club, and had concerns about the design of the scheme. The Chairman of the Panel recommended that detailed concerns be sent to Development Control Team in writing.
6. A local resident highlighted recent flooding on 9 and 11 June when gardens were flooded, sewage came up through manhole covers and residents had been unable to use toilets for a night, and that Thames Water must also be involved in the decision.
7. A resident who had previously worked as a Flood Defence Manager offered the opinion that use of the New River could be a potential alternative. He also highlighted the importance of maintenance and proactive management of water courses and culverts and questioned what maintenance had been carried out following the flooding in 2000. In respect of the flume construction at Enfield Golf Course, earth banks in flood conditions generated large amounts of silt, and he considered there was a need for a mechanical structure there. He requested a deferral of the planning decision ... view the full minutes text for item 6.
CLOSE OF MEETING
NOTED the closing points, including:
1. The Head of Development Management advised that any further comments should be sent to the Council's Planning Department, and would be received up until the date of the Planning Committee meeting to which the application would be presented for decision.
2. It was not expected that the application would be presented to a Planning Committee meeting until October 2012 at the earliest, as an ecology assessment needed to be carried out. It was expected that a special meeting of the Planning Committee would be convened at a large venue because of the level of public interest in this application.
3. Notes taken at this meeting would be appended to the Planning Officers' report to be considered by the Planning Committee.
4. Full details of the application were available from the Council's website www.enfield.gov.uk (Application Ref P12-01082PLA).
5. The Chairman thanked everyone for attending and contributing to the Planning Panel meeting. The Chairman suggested to the Environment Agency that they should consider producing alternative schemes with costs so that the public is convinced that the proposed scheme is the only viable one.


ADVERTISING & BROADCASTINGAlcohol advertising in the UK is regulated by the ASA through the CAP and BCAP Codes and Ofcom is responsible for TV programme sponsorship.
ALCOHOL MARKETING The Portman Group regulates all other alcohol marketing which is primarily UK targeted and not subject to regulation by the ASA or OfCom.
The Portman Group Alcohol Sponsorship Code came into effect to promote responsible drinking and support grass roots activities.
OTHER If you are looking for advice or guidance on another area of the alcohol industry please click here for a list of useful organisations.


Compressed sensing. This is an updated and reformatted version of my ANZIAM talk on this topic.
Discrete random matrices. This talk is a survey on recent developments on the universality phenomenon in random matrices, including work of myself and Van Vu. It covers similar material to my Netanyahu lecture, which has not previously appeared in electronic form.
Recent progress in additive prime number theory. This is an updated and reformatted version of my AMS lecture on this topic.
Recent progress on the Kakeya conjecture. This is an updated and reformatted version of my Fefferman conference lecture.
As always, comments, corrections, and other feedback are welcome.
I've just uploaded to the arXiv the paper A remark on partial sums involving the Möbius function, submitted to Bull. Aust. Math. Soc..
we give a sketch of the proof of these equivalences below the fold.
and the claim follows by bounding by .
where is the multiplicative semigroup generated by , i.e. the set of natural numbers whose prime factors lie in .
as the claim is trivial otherwise.
The claim now follows from (9), since and overlap only at .
One might hope that these inequalities (which gain a factor of over the trivial bound) might be useful when performing effective sieve theory, or effective estimates on various sums involving the primes or arithmetic functions.
This inequality (7) is so simple to state and prove that I must think that it was known to, say, Landau or Chebyshev, but I can't find any reference to it in the literature. [Update, Sep 4: I have learned that similar results have been obtained in a paper by Granville and Soundararajan, and have updated the paper appropriately.] The proof of (8) is a simple variant of that used to prove (7) but I will not detail it here.
I'll be in Australia for the next month or so, giving my share of the Clay-Mahler lectures at various institutions in the country. My first lecture is next Monday at Melbourne University, entitled "Mathematical research and the internet". This public lecture discusses how various internet technologies (such as blogging) are beginning to transform the way mathematicians do research.
A large portion of analytic number theory is concerned with the distribution of number-theoretic sets such as the primes, or quadratic residues in a certain modulus. At a local level (e.g. on a short interval ), the behaviour of these sets may be quite irregular. However, in many cases one can understand the global behaviour of such sets on very large intervals, (e.g. ), with reasonable accuracy (particularly if one assumes powerful additional conjectures, such as the Riemann hypothesis and its generalisations). For instance, in the case of the primes, we have the prime number theorem, which asserts that the number of primes in a large interval is asymptotically equal to ; in the case of quadratic residues modulo a prime , it is clear that there are exactly such residues in . With elementary arguments, one can also count statistics such as the number of pairs of consecutive quadratic residues; and with the aid of deeper tools such as the Weil sum estimates, one can count more complex patterns in these residues also (e.g. -point correlations).
However, suppose that instead of understanding the average-case behaviour of short intervals, one wants to control the worst-case behaviour of such intervals (i.e. to establish bounds that hold for all short intervals, rather than most short intervals). Then it becomes substantially harder to convert global information to local information. In many cases one encounters a "square root barrier", in which global information at scale (e.g. statistics on ) cannot be used to say anything non-trivial about a fixed (and possibly worst-case) short interval at scales or below. (Here we ignore factors of for simplicity.) The basic reason for this is that even randomly distributed sets in (which are basically the most uniform type of global distribution one could hope for) exhibit random fluctuations of size or so in their global statistics (as can be seen for instance from the central limit theorem). Because of this, one could take a random (or pseudorandom) subset of and delete all the elements in a short interval of length , without anything suspicious showing up on the global statistics level; the edited set still has essentially the same global statistics as the original set. On the other hand, the worst-case behaviour of this set on a short interval has been drastically altered.
One stark example of this arises when trying to control the largest gap between consecutive prime numbers in a large interval . There are convincing heuristics that suggest that this largest gap is of size (Cramér's conjecture). But even assuming the Riemann hypothesis, the best upper bound on this gap is only of size , basically because of this square root barrier. This particular instance of the square root barrier is a significant obstruction to the current polymath project "Finding primes".
On the other hand, in some cases one can use additional tricks to get past the square root barrier. The key point is that many number-theoretic sequences have special structure that distinguish them from being exactly like random sets. For instance, quadratic residues have the basic but fundamental property that the product of two quadratic residues is again a quadratic residue. One way to use this sort of structure to amplify bad behaviour in a single short interval into bad behaviour across many short intervals. Because of this amplification, one can sometimes get new worst-case bounds by tapping the average-case bounds.
Problem 1 What are the best bounds one can place on the first quadratic non-residue in the interval for a large prime ?
Probabilistic heuristics (presuming that each non-square integer has a 50-50 chance of being a quadratic residue) suggests that should have size , and indeed Vinogradov conjectured that for any . Using the Pólya-Vinogradov inequality, one can get the bound (and can improve it to using smoothed sums); combining this with a sieve theory argument (exploiting the multiplicative nature of quadratic residues) one can boost this to . Inserting Burgess's amplification trick one can boost this to for any . Apart from refinements to the factor, this bound has stood for five decades as the "world record" for this problem, which is a testament to the difficulty in breaching the square root barrier.
Note: in order not to obscure the presentation with technical details, I will be using asymptotic notation in a somewhat informal manner.
Van Vu and I have just uploaded to the arXiv our paper "Random matrices: Universality of local eigenvalue statistics up to the edge", submitted to Comm. Math. Phys.. This is a sequel to our previous paper, in which we studied universality of local eigenvalue statistics (such as normalised eigenvalue spacings ) for random matrices of Wigner type, i.e. Hermitian (or symmetric) random matrices in which the upper-triangular entries are independent with mean zero and variance one (for technical reasons we also have to assume an exponential decay condition on the distribution of the entries). The results in the previous paper were almost entirely focused on the bulk region, in which the index i of the eigenvalues involved was in the range . The main purpose of this paper is to extend the main results of the previous paper all the way up to the edge, thus allowing one to control all indices . As an application, we obtain a variant of Soshnikov's well-known result that the largest eigenvalue of Wigner matrices is distributed (after suitable normalisation) according to the Tracy-Widom law when the coefficients are symmetric, by assuming instead that the coefficients have vanishing third moment.
As one transitions from the bulk to the edge, the density of the eigenvalues decreases to zero (in accordance to the Wigner semicircular law), and so the average spacing between eigenvalues increases. (For instance, the spacing between eigenvalues in the bulk is of size , but at the extreme edge it increases to .) On the one hand, the increase in average spacing should make life easier, because one does not have to work at such a fine spatial scale in order to see the eigenvalue distribution. On the other hand, a certain key technical step in the previous paper (in which we adapted an argument of Erdos, Schlein, and Yau to show that eigenvectors of Wigner matrices were delocalised) seemed to require eigenvalue spacings to be of size , which was the main technical obstacle to extending the preceding results from the bulk to the edge.
The main new observation in the paper is that it was not the eigenvalue spacings which were of importance to eigenvalue delocalisation, but rather the somewhat smaller interlaced eigenvalue spacings , where is a minor of . The Cauchy interlacing law asserts that the latter is smaller than the former. But the interesting thing is that at the edge (when i is close to n), the interlaced spacings are much smaller than the former, and in particular remain of size about (up to log factors) even though the non-interlaced spacings increase to be as large as . This is ultimately due to a sort of "attractive force" on eigenvalues that draws them towards the origin, and counteracts the usual "eigenvalue repulsion effect", that pushes eigenvalues away from each other. This induces "bias" for eigenvalues to move in towards the bulk rescues the delocalization result, and the remainder of the arguments in our previous paper then continue with few changes.
Below the fold I wish to give some heuristic justification of the interlacing bias phenomenon, sketch why this is relevant for eigenvector delocalisation, and finally to recall why eigenvalue delocalisation in turn is relevant for universality.
The AKS test is of some relevance to the polymath project "Finding primes", so I thought I would sketch the details of the test (and the proof that it works) here. (Of course, full details can be found in the original paper, which is nine pages in length and almost entirely elementary in nature.) It relies on polynomial identities that are true modulo when is prime, but cannot hold for non-prime as they would generate a large number of additional polynomial identities, eventually violating the factor theorem (which asserts that a polynomial identity of degree at most can be obeyed by at most values of the unknown).
In the discussion on what mathematicians need to know about blogging mentioned in the previous post, it was noted that there didn't seem to be a single location on the internet to find out about mathematical blogs. Actually, there is a page, but it has been relatively obscure – the Mathematics/Statistics subpage of the Academic Blogs wiki. It does seem like a good idea to have a reasonably comprehensive page containing all the academic mathematics blogs that are out there (as well as links to other relevant sites), so I put my own maths blogroll onto the page, and encourage others to do so also (though you may wish to read the FAQ for the wiki first).
What do mathematicians need to know about blogging?
John Baez has been invited to write a short opinion piece for the Notices of the AMS to report about the maths blogging phenomenon to the wider mathematical community, and in the spirit of that phenomenon, has opened up a blog post to solicit input for that piece, over at the n-Category café. Given that the readers here are, by definition, familiar with mathematical blogging, I thought that some of you might like to visit that thread to share your own thoughts on the advantages and disadvantages of this mode of mathematical communication.
Problem 1. Find a deterministic algorithm which, when given an integer k, is guaranteed to locate a prime of at least k digits, in time polynomial in k.
Problem 2. Find a deterministic algorithm which, when given an integer k, is guaranteed to locate an adjacent pair n, n+1 of square-free numbers of at least k digits, in time polynomial in k.
Problem 3. Assume access to a factoring oracle. Find an algorithm which, when given an integer k, is guaranteed to find a prime of at least k digits (or an integer divisible by a prime of at least k digits) in time .
The current record time is unconditionally, or about on the Riemann hypothesis.
In the new research thread, a number of possible strategies are discussed, and will hopefully be explored soon. In addition to this thread, there is also the wiki page for the project, and a discussion thread aimed at more casual participants. Everyone is welcome to contribute to any of these three components of the project, as always.


text:
Boundaryless fish cause problems
Florida State University researchers say countries must work together on environmental management practices.
Boundaryless fish cause problems Florida State University researchers say countries must work together on environmental management practices. Check out this story on fsunews.com: http://fsune.ws/1Mh0Oaq
Tallahassee Published 3:30 a.m. ET July 9, 2015 | Updated 3:39 a.m. ET July 9, 2015
Fish don't care where political boundaries exist. That's why countries must work together on environmental management practices, according to Florida State University researchers.
Gag Grouper, a popular fish served in many coastal restaurants might be the prime example of a fish that knows no boundaries.
Felicia Coleman, director of the Florida State University Coastal and Marine Laboratory, and former FSU graduate student Nathaniel K. Jue — now an assistant professor at California State University, Monterrey Bay — write in the journal PLOS One that grouper off the coast of Florida in the Gulf of Mexico and those living near the Campeche Bank off Mexico are extremely similar.
By examining the genetic patterns of the gag grouper, Coleman and Jue were able to determine that the population of the gag grouper off of the Florida coast and the population off of the Mexican coast are not distinct groups, and they are dependent on each other for further reproduction.
For Coleman, the research highlights that biological systems transcend political boundaries and that current management practices need to be developed in coordination with other countries in order to protect grouper and other species living in the Gulf.
This research was funded by NOAA and the U.S. Environmental Protection Agency. Other authors on the paper are Christopher Koenig of the FSU Coastal and Marine Laboratory and Thierry Brulé of the Center of Investigation and Advanced Studies in Mexico.
Read or Share this story: http://fsune.ws/1Mh0Oaq
Stories from a pedicab driver: an inside look at Capital City Pedicabs
FSU grad student gives a voice to women in book 'How the End First Showed'
EXTRASENSORY: a different kind of art exhibit in FSU's MoFA
More Than Meets the Eye: FSU Student Hannah Kelsey is Crowned Miss Tallahassee 2020
25 years of the Downtown Tallahassee Market
The Fox & Stag: quality environment at a reasonable price

redpajama_set_name: RedPajamaCommonCrawl


Antoine Duhayot has starred in 1 movie. The 5 most recent movies Antoine Duhayot was in are listed below.
Next is the list of 39 actors/actresses that Antoine Duhayot has worked with spread over 2 pages. The list is sorted by the people Antoine Duhayot has worked most frequently with. When you find the person you are looking for, click on the link to view a list of movies they have worked in together.
If you decide instead to click on a movie with Antoine Duhayot, it will display the top billed cast. If the cast members have starred together in other movies; beneath the cast member a list will display.
Fanfan Fanfan and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Hélène Viaux and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Baptiste Roussillon and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Camille Japy and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
David Migeot and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Emilie Chesnais and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Grégory Gadebois and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Hacène Belkhadra and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Emmanuel Salinger and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Sandrine Kiberlain and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Patrick Mimoun and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Astrid Defrance and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Stephane Lagoutte and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Matthieu Boujenah and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Franck Tokarz and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Catherine Laporte and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Christophe Odent and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Marie-Frédérique Delestré and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Francis Leplay and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.
Michel Capitanio and Antoine Duhayot have starred in 1 movie together. Their first film was Très bien, merci in 2007.


Karen Millen Statement Lace & Knit - Black - EI068S91J | Memberstartup.com: ALL clothes for every seasons online shop.
Black knitted jumper with lace sleeves. This black jumper features intricate black lacing on the upper body both front and back it also features full lace sleeves. The top is finished with a ribbed hem and cuffs.


text:
Love Dream est un film italien, sorti en 1988.

Synopsis

Fiche technique
 Titre français : Love Dream
 Réalisation : Charles Finch
 Scénario : Charles Finch
 Photographie : Luciano Tovoli
 Pays d'origine : Italie
 Genre : fantastique
 Date de sortie : 1988

Distribution
 Christophe Lambert : Menrou
 Diane Lane : China
 Francesco Quinn : Peter
 Cláudia Ohana : Lisa
 J. C. Quinn : Willy
 Monica Scattini : Nicoletta
 Joaquim de Almeida

Liens externes

Film italien sorti en 1988
Film fantastique italien

redpajama_set_name: RedPajamaWikipedia


Hood for a 1999-2007 F-250, F-350, F-450, F-550. This is a brand new stock replacement hood. It is a Keystone. It is brand new never been installed. There are a few very minor dings in it. It is factory black primer.


Much useful information on healthy nutrition has already been published. For that reason, I only want to concentrate on the basic principles of a healthy and well-balanced diet here.
Of course, we should make sure not to eat too much animal fat, too many carbohydrates and most of all avoid refined sugar. In the meantime I believe most people are aware of the fact that vegetables, fruits and mushrooms should be prioritised in healthy diets.
Adhering to a healthy and well-balanced diet helps to ensure our body's sufficient supply with the nutrients it needs for proper vital processes.
However, the food also has to be digested and made available to the body's cells via the bloodstream.
So, chewing the food in our mouth is already one of the basic conditions for a healthy diet and digestion. In my opinion, the most serious mistakes in terms of nutrition are already made at this point. We have forgotten the fact that digestion - i.e. releasing the vital substances - begins in our mouth.
It is important to know that what we fail to do in our mouth as the first step in the digestion process cannot be made up for at any later stage, e.g. in the stomach or intestines. This alone reveals the importance of proper chewing.
Chewing does not only serve to reduce the food to small pieces. By insalivating it intensely, we also change the food's pH value. Saliva has a neutral pH value of about 7. Thorough chewing can thus convert any food's pH value towards an alkaline one. This is important because the pH value in our stomach generally ranges between 1 and 3. The higher the difference in pH value, the easier it is for our body to break down the food and the more vital substances derived from food can be made available to the body cells.
Thorough chewing - which means that every bite should be chewed about 50 times - is also very supportive for those who frequently suffer from heartburn, and is the first step in overcoming this unpleasant disorder.
However, one frequently hears: "I don't have the time to chew each bite 50 times!". Yet, if we eat only half as much in the time that we have for our meals because we chew the food more thoroughly, we release our body from the stress of large-scale digestion processes. Due to the increased efficiency made possible by thorough chewing, our body cells are provided with the same amount of vital substances that would be available if we ate twice as much. The body can then use its precious energies for other important things such as repair processes.
Scientific studies have already verified the positive virtues of various fruits and vegetables. Thus, modern science recommends consuming fruits and vegetables of all five colours daily to ensure our organism is provided with the entire nutrient range.
Due to their specific nutrients, mushrooms as vegetables should be an integral part of a healthy diet. Mushrooms are the only kind of food that has wood as a nutrient basis. Only mushrooms subsist on wood and thus provide us with nutrients, vitamins and minerals not found in any other food.
Mushrooms have high vitamin B content. They are also rich in ergosterol, a vitamin D precursor, and vitamin E. Moreover, they contain high amounts of minerals, and some of them contain all eight essential amino acids required for cell formation. This is of particular importance for all those who aim at reducing their meat consumption, i.e. especially for vegetarians and vegans. Mushrooms furthermore contain all eight glyconutrients, i.e. essential sugar, which is crucial for proper cell information. This cell information is not only vital in the treatment of cancer but generally for our immune system's regulation.
Important for all those who wish to reduce their weight or avoid weight gains in general also is the fact that mushrooms are low-calorie and barely contain any fat. Of course this is also an important aspect for those with diabetes type II or the metabolic syndrome. Moreover, one should know that mushrooms have blood-sugar lowering properties due to their ingredients.
Those who cannot or do not want to eat a small serving of mushrooms every day can compensate this with mushroom powder capsules. Different fruits and vegetables plus mushrooms ensure a balanced diet. Important though, as already mentioned, is to remember to chew every bite at least 50 times.
No less important it is to take the time to prepare and arrange our meals on the plate and to acknowledge that we eat with our eyes first. We should pay great attention to our meals so that we can fully enjoy and properly digest our food.
Proper eating habits and healthy ingredients can also help adjust our day-night rhythm. Thus we should consume stimulating foods in the morning and calming ones in the evening. In general, protein-rich foods have rather stimulating properties while vegetables are rather soothing. Vegetables and mushrooms should thus also be eaten in the evening.
People whose feet, hands and nose tip are frequently cold suffer from energetic renal insufficiency and should thus avoid raw vegetables. They should always serve vegetables warm but avoid overcooking them: the vegetables should still be firm enough that one must chew them.
Finally, I would like to mention that the old saying "In the mornings, eat like a king, at noon like a nobleman, and at night like a beggar" still applies.
If we observe this old wisdom, we may confidently hope to reach an old age in good health.


Great deals on sweet rides from Porsche to Ferrari and Rolls Royce to Aston Martin.
This black on black, 2004 Ferrari 348 Spider is sure not to disappoint you. It's an open top Spider and a gorgeous ride. Looks to be well maintained with recent engine out service completed. Clean title and 65k miles on the car. This one is a car to drive and enjoy.
This is one heck of a Ferrari bargain. A 1989 Ferrari 348 ts currently at $17,500. Classic Ferrari Corsa Red with Tan interior. Just over 34k miles on it with a clear title. It's a fixer upper, but at that price, you could afford a $10k to $12k maintenance bill and STILL have a bargain on your hands. Sure there are always risks with a non-running Ferrari, but the potential reward is there. Especially for someone who is willing to dig in with some elbow grease.
I love the Ferrari 348. It's like a more manageable version of the Ferrari Testarossa with the same great looks of the iconic 80's supercar. I miss my 348 every sunny day we have in the Northwest.
Fortunately there are still great deals to be had on these great cars. This is a perfect example of one. A 1990 Ferrari 348 ts in the classic red with tan interior. Just over 45k miles on the odo and appears to be up to date on service.
Beautiful Ferrari for sale by owner. Starts easy, runs like new. NO FLUID LEAKS. Expensive engine-out service has been performed and documented. No current major service required. Ready to drive anywhere. Climate control, 19″ Challenge rims and new tires, so it rides low, and corners flat. All leather interior, 4-point belts, good paint but not concours quality. Includes factory leather toolbox with tools. All maintenance documents provided, always pampered and garaged, just passed California emissions.
Buy It Now on the auction is $31,000. One heck of a great deal for a Ferrari 348 that's up to date with documented service points.
I still think the Ferrari 348 is one of the few bargain Ferraris left out there. It embodies everything that makes a Ferrari a Ferrari, yet has not been picked up by the enthusiasts and priced out of the ballpark for many who dream of owning a Ferrari.
Today is a 1991 Ferrari 348 ts. Just 47k miles on her. Red with tan interior…absolutely THE color combo for a Ferrari of this era in my opinion. Even includes original Ferrari luggage and floor mats.
THE CONDITION IS ABSOLUTELY MINT!!! The paint and the body are shiny and in great condition. Interior is in Great shape, with almost no wear. Exterior is in good condition. There is on small blemish on the edge of drivers door please refer to the picture. Rims and tires are in great condtion. Everything works AC, CD Player, the vehicle drives and shifts perfect. All suspension is operating as it should. Also there is a small oil leak trips about quarter size in a week. All pictures are recent. The previous owner took excellent care of this Ferrari, and it shows! Tires (front 70%) (back 70%), non-smoker, Certified Real car from a Licensed and bonded dealer 100% clear title.
Get this…the auction ended at $30,995. A HECK of a deal!
There are lots of Ferrari bargains out there if you're willing to look.
I love the Ferrari 348 ts. I owned one for a year and a half. Was a heck of a great car. Today's bargain is a killer deal.
I know these cars and knew immediately when I found it, that it was the only one I've looked at without major bolster wear, seat redyes, sticky plastic, oil leaks, slow windows, paintwork etc etc, that this one was special and has none of these issues!. The car is a very, very nice driver, very, very nice cosmetics with absolutely zero known mechanical defects of any kind, and everything works.
This is a heck of a bargain at under $30k. Current auction price is $22,100. Buy It Now price is $29,500.
Check out the car at the eBay auction page here:Ferrari 348 Bargain .
I love the Ferrari 348. A red 1990 Ferrari 348ts (featured in the early days on BargainExotics.com) was my first Ferrari and I would buy another one in a heartbeat. It was a great car and a blast to drive. I love the styling and the resemblance to the Ferrari Testarossa.
Absolutely pristine, rare color combination, super low mileage, original paint, accident free, show quality 348 TS finished in Bianco (White) over lipstick red leather interior with black upper hides and red carpets. This is a locally owned car that has always been serviced here by it's previous owner who has had the car for the past 13 years. He purchased it in 1997 from the local Porsche dealer where it was traded on a new Porsche and just sold it to us as he was retiring and moving to Florida. The paint is all original except for the usual front bumper painted for stone chips. The paint is in perfect condition with no dings, dents, or scratches to be found anywhere. It has the usual stress marks where the c pillars meet the quarters, but otherwise the paint is absolutely flawless. The interior of this car is absolutely incredible. It has none of the wear usually found on a Ferrari of this vintage. There is absolutely no dash shrinkage, no faded carpets, no worn out seats, shrunken door panels, and no gummy or scratched center dash plastics. The car had the original wheels when we purchased it but upgraded them with a set of all new Modular style 18″ wheels with all new Z-Rated max performance tires. The original wheels are included with the car. In addition, this car has a stainless steel tubi exhaust system and sounds as great as it looks. This car runs and drives absolutely like new with no problems, issues, or vibrations whatsoever. This car is absolutely incredible inside, outside, and the way it sounds and drives. It has been regularly serviced with yearly maintenances only. I have no record of any major service, although one may have been done without my knowledge. I have just had the car fully serviced in our ASE Master Ferrari service department including all fluid flushed and a complete check over. We have also completed a full compression and leakdown test for your piece of mind with no problems found whatsoever. It comes complete with all the books in the original leather binder. If you are looking for the cleanest, best color combination, low mileage 348 around, don't miss out on this pristine example. Compare this to any others for sale and there is no comparison, this car stands shoulders above the rest.
This is up for $36,995. I'd make an offer of $32k or $33k. When the exotic car market comes back around, this should easily move up to the $40k range.
Here's a link to the eBay auction page: 1990 Ferrari 348 TS .


Missouri became the "Gateway to the West" for half a million emigrants seeking a better life, quick wealth, or adventure on the frontier. Independence, Westport, and St. Joseph developed into bustling outfitting posts for the three major trails headed west: Oregon, California, and Santa Fe. The first true emigrant train left Missouri in 1841 guided by Thomas Fitzpatrick, and the first major migration to Oregon passed through the area in 1843.
Caravans left Independence in the early spring on the road to West Port. The California, Oregon and Santa Fe Trails were, it should be noted, one and the same along this route. It was after they left West Port that they divided and took on their respective, singular names. (Lee, F. (1980, May). Historic Westport: The Trails and how they passed through Westport. Westport. 6. MVSC Q 977.8411 W537).
Of those who set out in the spring of 1850 was a large party among whose members was Rev. Robert James, the father then of two little prattling boys, who afterwards became the noted bandits, Frank and Jesse. En route Mr. James wrote one letter to the Liberty Tribune, which is still preserved in the files of that paper. Not long after his arrival in California, Rev. James died. (History of Clay and Platte Counties. (1885). St. Louis, MO: National Historical Co., pg. 153. MVSC 977.816 C62-2).
"We hold tent worship nightly in some one of our tents and every Sabbath evening prayer meetings. Many of the emigrants are in great distress. Some are going badly prepared for the trip. One man is going through with a wheel barrow, who out travels our mule teams … May the blessings of God rest on us until we shall have completed our expedition and return home safely to our families and friends." (James, R. (1850, May 18). [Letter to Liberty Tribune]. Fort Laramie, WY. Liberty (MO) Tribune Papers (SC34).
This letter is now in the Missouri Valley Special Collections Liberty (Mo.) Tribune Papers (SC34). Another letter written to the Liberty Tribune, this one by N. P. Carpenter from Sacramento City, California, Dec. 9, 1849, advises only "able-bodied" men to venture on the trail.
"I would not advise any man, who is engaged in business that will yield him a decent support, to come and risk his fortunes here---A young, stout, able-bodied man, who is willing to undergo a great deal of hard labor, had, perhaps, better come. All lazy people had better stay away." (Carpenter, N. P. (1849, December 9). [Letter to Liberty Tribune]. Sacramento City, California. Liberty (MO) Tribune Papers (SC34).
Chase, G. M. (1860). George M. Chase Diary. SC31-2.
Gass, P. (1807). 1807 Patrick Gass Journal. MVSC X 917.8 G25J 1807.
Hines, M. E. (1958). Diary of Mary Everard Hines. Manuscript file: Hines, Mary Everard.
Carpenter, D. (1847-1913). Dan Carpenter's [Journal] 1847-1848, 1850-1851.
Chambers, A. J. (1845). Crossing the Plains in 1845.
Cox, M. C. (1953). James Hyatt McGee.
Map of California, Oregon, Texas, and the Territories Adjoining with Routes Etc. (1849). SC117, Series 3-12: U.S. & States #13.
Pioneer Map of Jackson County, Missouri. (1934). SC117, Series 3-8: Jackson County & Independence, Missouri #11.


a maze of death Download a maze of death or read online books in PDF, EPUB, Tuebl, and Mobi Format. Click Download or Read Online button to get a maze of death book now.... F e a t u r e sFeatures This image released by Twentieth Century Fox shows Kaya Scodelario (left), and Patricia Clarkson in a scene from 'Maze Runner: The Death Cure'.
Maze Runner: The Death Cure builds on the propulsive second film, affording each member of cast with a moment to shine in welcome lulls between spectacular set pieces.


text:
* Proposal: [SE-0228](0228-fix-expressiblebystringinterpolation.md)
* Authors: [Brent Royal-Gordon](https://github.com/brentdax), [Michael Ilseman](https://github.com/milseman)
* Review Manager: [Doug Gregor](https://github.com/DougGregor)
* Status: **Implemented (Swift 5)**
* Review: [Discussion thread](https://forums.swift.org/t/se-0228-fix-expressible-by-string-interpolation/16031), [Announcement thread](https://forums.swift.org/t/accepted-se-0228-fix-expressible-by-string-interpolation/16548)
* Implementation: [apple/swift#20214](https://github.com/apple/swift/pull/20214)

## Introduction

String interpolation is a simple and powerful feature for expressing complex, runtime-created strings, but the current version of the `ExpressibleByStringInterpolation` protocol has been deprecated since Swift 3. We propose a new design that improves its performance, clarity, and efficiency.

Swift-evolution thread: [\[Draft\] Fix ExpressibleByStringInterpolation](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170306/033676.html), [String interpolation revamp](https://forums.swift.org/t/string-interpolation-revamp/9302), [String interpolation revamp: design decisions](https://forums.swift.org/t/string-interpolation-revamp-design-decisions/12624)

## Motivation

### Background

An interpolated string literal contains one or more embedded expressions, delimited by `\(` and `)`. At runtime, these expressions are evaluated and concatenated with the string literal to produce a value. They are typically more readable than code that switches between string literals, concatenation operators, and arbitrary expressions.

Like most literal features in Swift, interpolated string literals are implemented with a protocol, `ExpressibleByStringInterpolation`. However, this protocol has been known to have issues since Swift 3, so it is currently deprecated.

### Desired use cases

We see three general classes of types that might want to conform to `ExpressibleByStringInterpolation`:

1. **Simple textual data**: Types that represent simple, unconstrained text, like `Swift.String` itself. String types from foreign languages (like `JavaScriptCore.JSValue`) and alternative representations of strings (like a hypothetical `ASCIIString` type) might also want to participate in string interpolation.

2. **Structured textual data**: Types that represent text but have some additional semantics. For example, a `Foundation.AttributedString` type might allow you to interpolate dictionaries to set or clear attributes. [This gist's `LocalizableString`][loc] type creates a format string, which can be looked up in a `Foundation.Bundle`'s localization tables.

3. **Machine-readable code fragments**: Types that represent data in a format that will be understood by a machine, like [`SQLKit.SQLStatement`][sql] or [this blog post's `SanitizedHTML`][html]. These types often require data included in them to be escaped or passed out-of-band; a good `ExpressibleByStringInterpolation` design might allow this to be done automatically without the programmer having to do anything explicit. They may only support specific types, or may want to escape by default but also have a way to insert unescaped data.

The current design handles simple textual data, but struggles to support structured textual data and machine-readable code fragments.

  [sql]: https://github.com/brentdax/SQLKit/blob/master/Sources/SQLKit/SQLStatement.swift
  [html]: https://oleb.net/blog/2017/01/fun-with-string-interpolation/
  [loc]: https://gist.github.com/brentdax/79fa038c0af0cafb52dd

### Current design

The compiler parses a string literal into a series of *segments*, each of which is either a *literal segment* containing characters and escapes, or an *interpolated segment* containing an expression to be interpolated. If there is more than one segment, it wraps each segment in a call to `init(stringInterpolationSegment:)`, then wraps all of the segments together in a call to `init(stringInterpolation:)`:

```swift
// Semantic expression for: "hello \(name)!"
String(stringInterpolation:
  String(stringInterpolationSegment: "hello "),
  String(stringInterpolationSegment: name),
  String(stringInterpolationSegment: "!"))
```

The type checker considers all overloads of `init(stringInterpolationSegment:)`, not just the one that implements the protocol requirement. `Swift.String` uses this to add fast paths for types conforming to `CustomStringConvertible` and `TextOutputStreamable`.

### Issues with the current design

The current design is inefficient and inflexible for conformers. It does not permit special handling such as formatting or interpolation options.

#### Inefficient: Naïve memory management

Each `init(stringInterpolationSegment:)` call creates a temporary instance of `Self`; these instance are then concatenated together. Depending on the conformer or the segment size, this may trigger a heap allocation and ARC overhead for every single interpolated segment.

Furthermore, while the compiler knows the sizes and numbers of literal and interpolated segments, this is not communicated to the conformer.

If size information were available to the conformer, they could estimate the final size of the value and preallocate capacity. If segments were not converted to `Self` before concatenation, their data could be directly written to this preallocated capacity without using temporary instances.

#### Inflexible: No extra parameters, unconstrained segments, lost segment semantics

The current approach does not permit conformers to specify additional parameters or options to govern the evaluation of an interpolated expression. Many conformers may want to provide alternative interpolation behaviors, such as disabling escaping in `SanitizedHTML`. Others may want to accept options, like controlling the format string used in a `LocalizableString`. `String` itself would like to support a format argument eventually.

`init(stringInterpolationSegment:)` takes an unconstrained generic value, so its parameter can be of any type. However, some conformers may want to limit the types that can be interpolated. For example, `SQLKit.SQLStatement` can only bind certain types, like integers and strings, to a SQL statement's parameters.

This unconstrained generic parameter causes a second problem: when a literal is passed to `init(stringInterpolationSegment:)`, it defaults to forming a `String`, the default literal type. This deviates from the standard library's common practice of allowing the conformer to supply a literal type for use.

Finally, the conformer cannot easily determine whether an incoming segment was from a literal or an expression without resorting to hacks baking in compiler-internal details.

Compiler-internal details

##### Baking in assumptions

An `init(stringInterpolationSegment:)` implementation cannot determine whether its parameter is a literal segment or an interpolated segment. However, the `init(stringInterpolation:)` call can exploit a compiler quirk to do so: the parser always generates a literal segment first, and always alternates between literal and interpolated segments (generating empty literal segments if necessary), so the position of a segment can tell you whether it is literal or interpolated.

Needless to say, this is the sort of obscure implementation detail we don't want users to depend upon. And preserving enough data for `init(stringInterpolation:)` to treat a segment as either type often requires conformers to add extra properties or otherwise alter the type's design purely to support string interpolation.

##### Type-checker hacks

If semantic analysis simply generated the semantic expression and then type-checked it normally, many string interpolations would be too complex to type-check. Instead, it type-checks each segment separately, then creates the `init(stringInterpolationSegment:)` call for the segment and type-checks just the one call to resolve its overload.

String interpolation is the only remaining client of this type-checker entry point; we want to get rid of it.

### Potential uses

An improved string interpolation design could open many doors for future functionality in the standard library, in framework overlays, and in user code. To illustrate, here are some things we could use it for in code shipped with the Swift compiler. We're not proposing any of this, and any future proposal might look different—we're just demonstrating what's possible.

#### Constructing formatted strings

There are a number of approaches we could take to formatting values interpolated into strings. Here are a few examples with numbers:

```swift
// Use printf-style format strings:
"The price is $\(cost, format: "%.2f")"

// Use UTS #35 number formats:
"The price is \(cost, format: "¤###,##0.00")"

// Use Foundation.NumberFormatter, or a new type-safe native formatter:
"The price is \(cost, format: moneyFormatter)"

// Mimic String.init(_:radix:uppercase:)
"The checksum is 0x\(checksum, radix: 16)"
```

You could imagine analogous formatting tools for other types, like `Data`, `Date`, or even just `String` itself.

#### Logging

Some logging facilities restrict the kinds of data that can be logged or require extra metadata on certain values; a more powerful interpolation feature could support that:

```swift
log("Processing \(public: tagName) tag containing \(private: contents)")
```

#### Constructing attributed strings

`NSAttributedString` or a value-type wrapper around it could allow users to interpolate dictionaries of attributes to enable and disable them:

```swift
"\([.link: supportURL])Click here\([.link: nil]) to visit our support site"
```

#### Localization

A `LocalizableString` type could be expressed by a string literal, which would be used to generate a format string key and a list of arguments; converting a `LocalizableString` to an ordinary `String` would look up the key in a `Bundle`'s localization table, then format the value with the arguments.

```swift
// Builds a LocalizableString(key: "The document "%@" could not be saved.", arguments: [name])
let message: LocalizableString = "The document "\(name)" could not be saved."
alert.messageText = String(localized: message)
```

## Proposed solution

We propose completely reworking the currently-deprecated `ExpressibleByStringInterpolation` as follows (doc comments omitted for brevity):

```swift
public protocol ExpressibleByStringInterpolation
  : ExpressibleByStringLiteral {

  associatedtype StringInterpolation : StringInterpolationProtocol
    = String.StringInterpolation
    where StringInterpolation.StringLiteralType == StringLiteralType

  init(stringInterpolation: StringInterpolation)
}

public protocol StringInterpolationProtocol {
  associatedtype StringLiteralType : _ExpressibleByBuiltinStringLiteral

  init(literalCapacity: Int, interpolationCount: Int)

  mutating func appendLiteral(_ literal: StringLiteralType)

  // Informal requirement: mutating func appendInterpolation(...)
}
```

An interpolated string will be converted into code that:

1. Initializes an instance of an associated `StringInterpolation` type, passing the total literal segment size and interpolation count as parameters.

2. Calls its `appendLiteral(_:)` method to append literal values, and `appendInterpolation` to append its interpolated values, one at a time. Interpolations are treated as call parentheses—that is, `\(x, with: y)` becomes a call to `appendInterpolation(x, with: y)`.

3. Passes the instance to `init(stringInterpolation:)` to produce a final value.

Below is code roughly similar to what the compiler would generate:

```swift
// Semantic expression for: "hello \(name)!"
String(stringInterpolation: {
  var temp = String.StringInterpolation(literalCapacity: 7, interpolationCount: 1)
  temp.appendLiteral("hello ")
  temp.appendInterpolation(name)
  temp.appendLiteral("!")
  return temp
}())
```

[We have written a few examples of conforming types.][examples]

  [examples]: https://gist.github.com/brentdax/0b46ce25b7da1049e61b4669352094b6

## Detailed design

This design has been implemented in [apple/swift#18590](https://github.com/apple/swift/pull/18590).

### The `StringInterpolation` type

The associated `StringInterpolation` type is a sort of buffer or scratchpad where the value of an interpolated string literal is accumulated. By having it be an associated type, rather than `Self` as it currently is, we realize a few benefits:

1. A new type can serve as a namespace for the various `appendLiteral` and `appendInterpolation` methods. This allows conformers to add new interpolation methods without them showing up in code completion, documentation, etc.

2. A separate type can store extra temporary state involved in the formation of the result. For example, `Foundation.AttributedString` might need to track the current attributes in a property; a type backed by a parsed data structure, like a `LambdaCalculusExp` or `Regexp` type, could store an unparsed string or parser state. When a type does *not* need any extra state, the associated type does not add any overhead.

3. Several different types can share an implementation. For instance, `String` and `Substring` both use a common `StringInterpolationProtocol`-conforming type.

The standard library will provide a `DefaultStringInterpolation` type; `StringProtocol`, and therefore `String` and `Substring`, will use this type for their interpolation. (`Substring` did not previously permit interpolation.)

The standard library will also provide two sets of default implementations:

* For types using `DefaultStringInterpolation`, it will provide a default `init(stringInterpolation:)` that extracts the value after interpolation and forwards it to `init(stringLiteral:)`. Thus, types that currently conform to `ExpressibleByStringLiteral` and use `String` as their literal type can add simple interpolation support by merely changing their conformance to `ExpressibleByStringInterpolation`.

* For other types, it will provide a default `init(stringLiteral:)` that constructs a `Self.StringInterpolation` instance, calls its `appendLiteral(_:)` method, and forwards it to `init(stringInterpolation:)`. (An unavailable or deprecated `init(stringLiteral:)` will ensure that this is never used with the `init(stringInterpolation:)` provided for `DefaultStringInterpolation`-using types, which would cause infinite recursion.)

### The `appendInterpolation` method(s)

`StringInterpolation` types must conform to a `StringInterpolationProtocol`, which requires the `init(literalCapacity:interpolationCount:)` and `appendLiteral(_:)` methods.

Non-literal segments are restricted at compile time to the overloads of `appendInterpolation` supplied by the conformer. This allows conforming types to restrict the values that can be interpolated into them by implementing only methods that accept the types they want to support. `appendInterpolation` can be overloaded to support several unrelated types.

`appendInterpolation` methods can specify any parameter signature they wish. An `appendInterpolation` method can accept multiple parameters (with or without default values), can require a label on any parameter (including the first one), and can have variadic parameters. `appendInterpolation` methods can also throw; if one does, the string literal must be covered by a `try`, `try?`, or `try!` keyword. Future work includes enhancing String to accept formatting control.

While this part of the design gives us great flexibility, it does introduce an implicit relationship between the compiler and ad-hoc methods declared by the conformer. It also restricts what values can be interpolated in a context generic over `StringInterpolationProtocol`, though further constraints can lift this restriction.

Even though there is no formal requirement listed in the protocol, we have modified the compiler to emit an error if a `StringInterpolationProtocol`-conforming type does not have at least one overload of `appendInterpolation` that is as public as the type, does not return a value (or returns a discardable value), and is not static.

### Interpolation parsing changes

Interpolations will be parsed as argument lists; labels and multiple parameters will be permitted, but trailing closures will not.

This change is slightly source-breaking: a 4.2 interpolation like `\(x, y)`, which tries to interpolate a tuple, would need to be written `\((x, y))`. While we could address un-labeled tuples with n-arity overloads of `appendInterpolation`, labeled tuples would still break. We emulate the current behavior in Swift 4.2 mode, and we can easily correct it during migration to Swift 5.

### Ancillary changes

We will add `ExpressibleByStringInterpolation` conformance to `StringProtocol`, and thus to `Susbtring`, allowing interpolations in string literals used to create `Substring`s.

We will add `TextOutputStreamable` conformances to `Float`, `Double`, and `Float80`, along with an underscored, defaulted method for writing raw ASCII buffers to `TextOutputStream`s. These changes together reduce a regression in `Float` interpolation benchmarks and completely reverse regressions in `Double` and `Float80` interpolation benchmarks.

### Implementation details

The `DefaultStringInterpolation` type

The standard library uses `make()` to extract the final value; `CustomStringConvertible` is provided as a public equivalent for types that want to use `DefaultStringInterpolation` but do some processing in their `init(stringInterpolation:)` implementation.

```swift
/// Represents a string literal with interpolations while it is being built up.
///
/// Do not create an instance of this type directly. It is used by the compiler
/// when you create a string using string interpolation. Instead, use string
/// interpolation to create a new string by including values, literals,
/// variables, or expressions enclosed in parentheses, prefixed by a
/// backslash (`\(`...`)`).
///
///     let price = 2
///     let number = 3
///     let message = "If one cookie costs \(price) dollars, " +
///                   "\(number) cookies cost \(price * number) dollars."
///     print(message)
///     // Prints "If one cookie costs 2 dollars, 3 cookies cost 6 dollars."
///
/// When implementing an `ExpressibleByStringInterpolation` conformance,
/// set the `StringInterpolation` associated type to `DefaultStringInterpolation`
/// to get the same interpolation behavior as Swift's built-in `String` type and
/// construct a `String` with the results. If you don't want the default behavior
/// or don't want to construct a `String`, use a custom type conforming to
/// `StringInterpolationProtocol` instead.
///
/// Extending default string interpolation behavior
/// ===============================================
///
/// Code outside the standard library can extend string interpolation on
/// `String` and many other common types by extending
/// `DefaultStringInterpolation` and adding an `appendInterpolation(...)`
/// method. For example:
///
///     extension DefaultStringInterpolation {
///         fileprivate mutating func appendInterpolation(
///                  escaped value: String, asASCII forceASCII: Bool = false) {
///             for char in value.unicodeScalars {
///                 appendInterpolation(char.escaped(asASCII: forceASCII)
///             }
///         }
///     }
///
///     print("Escaped string: \(escaped: string)")
///
/// See `StringInterpolationProtocol` for details on `appendInterpolation`
/// methods.
///
/// `DefaultStringInterpolation` extensions should add only `mutating` members
/// and should not copy `self` or capture it in an escaping closure.
@_fixed_layout
public struct DefaultStringInterpolation: StringInterpolationProtocol {
  /// The string contents accumulated by this instance.
  @usableFromInline
  internal var _storage: String = ""

  /// Creates a string interpolation with storage pre-sized for a literal
  /// with the indicated attributes.
  ///
  /// Do not call this initializer directly. It is used by the compiler when
  /// interpreting string interpolations.
  @inlinable
  public init(literalCapacity: Int, interpolationCount: Int) {
    let capacityPerInterpolation = 2
    let initialCapacity = literalCapacity + interpolationCount * capacityPerInterpolation
    _storage.reserveCapacity(initialCapacity)
  }

  /// Appends a literal segment of a string interpolation.
  ///
  /// Do not call this method directly. It is used by the compiler when
  /// interpreting string interpolations.
  @inlinable
  public mutating func appendLiteral(_ literal: String) {
    _storage += literal
  }

  /// Interpolates the given value's textual representation into the
  /// string literal being created.
  ///
  /// Do not call this method directly. It is used by the compiler when
  /// interpreting string interpolations. Instead, use string
  /// interpolation to create a new string by including values, literals,
  /// variables, or expressions enclosed in parentheses, prefixed by a
  /// backslash (`\(`...`)`).
  ///
  ///     let price = 2
  ///     let number = 3
  ///     let message = "If one cookie costs \(price) dollars, " +
  ///                   "\(number) cookies cost \(price * number) dollars."
  ///     print(message)
  ///     // Prints "If one cookie costs 2 dollars, 3 cookies cost 6 dollars."
  @inlinable
  public mutating func appendInterpolation<T: TextOutputStreamable & CustomStringConvertible>(_ value: T) {
    value.write(to: &_storage)
  }

  /// Interpolates the given value's textual representation into the
  /// string literal being created.
  ///
  /// Do not call this method directly. It is used by the compiler when
  /// interpreting string interpolations. Instead, use string
  /// interpolation to create a new string by including values, literals,
  /// variables, or expressions enclosed in parentheses, prefixed by a
  /// backslash (`\(`...`)`).
  ///
  ///     let price = 2
  ///     let number = 3
  ///     let message = "If one cookie costs \(price) dollars, " +
  ///                   "\(number) cookies cost \(price * number) dollars."
  ///     print(message)
  ///     // Prints "If one cookie costs 2 dollars, 3 cookies cost 6 dollars."
  @inlinable
  public mutating func appendInterpolation<T: TextOutputStreamable>(_ value: T) {
    value.write(to: &_storage)
  }

  /// Interpolates the given value's textual representation into the
  /// string literal being created.
  ///
  /// Do not call this method directly. It is used by the compiler when
  /// interpreting string interpolations. Instead, use string
  /// interpolation to create a new string by including values, literals,
  /// variables, or expressions enclosed in parentheses, prefixed by a
  /// backslash (`\(`...`)`).
  ///
  ///     let price = 2
  ///     let number = 3
  ///     let message = "If one cookie costs \(price) dollars, " +
  ///                   "\(number) cookies cost \(price * number) dollars."
  ///     print(message)
  ///     // Prints "If one cookie costs 2 dollars, 3 cookies cost 6 dollars."
  @inlinable
  public mutating func appendInterpolation<T: CustomStringConvertible>(_ value: T) {
    _storage += value.description
  }

  /// Interpolates the given value's textual representation into the
  /// string literal being created.
  ///
  /// Do not call this method directly. It is used by the compiler when
  /// interpreting string interpolations. Instead, use string
  /// interpolation to create a new string by including values, literals,
  /// variables, or expressions enclosed in parentheses, prefixed by a
  /// backslash (`\(`...`)`).
  ///
  ///     let price = 2
  ///     let number = 3
  ///     let message = "If one cookie costs \(price) dollars, " +
  ///                   "\(number) cookies cost \(price * number) dollars."
  ///     print(message)
  ///     // Prints "If one cookie costs 2 dollars, 3 cookies cost 6 dollars."
  @inlinable
  public mutating func appendInterpolation<T>(_ value: T) {
    _print_unlocked(value, &_storage)
  }

  /// Creates a string from this instance, consuming the instance in the process.
  @inlinable
  internal __consuming func make() -> String {
    return _storage
  }
}

extension DefaultStringInterpolation: CustomStringConvertible {
  @inlinable
  public var description: String {
    return _storage
  }
}
```

Generating the append calls

This design puts every `appendLiteral(_:)` and `appendInterpolation` call in its own statement, so there's no need for special type checker treatment. Each interpolation will naturally be type-checked separately, and the overloads of `appendInterpolation` will be resolved at the same time as the value being interpolated. This helps us with ongoing refactoring of the type checker.

Due to issues with capturing of partially initialized variables, we do not enclose these statements in a closure. Instead, we use a new kind of AST node.

Performance

While some string interpolation benchmarks show regressions of 20–30%, most show improvements, sometimes dramatic ones.

| Benchmark                                    | -O speed improvement | -Osize speed improvement |
| -------------------------------------------- | -------------------- | ------------------------ |
| `StringInterpolationManySmallSegments`       | 2.15x                | 1.80x                    |
| `StringInterpolationSmall`                   | 2.01x                | 2.03x                    |
| `ArrayAppendStrings`                         | 1.16x                | 1.14x                    |
| `FloatingPointPrinting_Double_interpolated`  | 1.15x                | 1.16x                    |
| `FloatingPointPrinting_Float80_interpolated` | 1.09x                | 1.08x                    |
| `StringInterpolation`                        | 0.82x                | 0.79x                    |
| `FloatingPointPrinting_Float_interpolated`   | 0.82x                | 0.73x                    |

The `StringInterpolation` benchmark's regression is caused by the specific sizes of literal and interpolated segment sizes; in the new design, these happen to cause the benchmark to grow its buffer an extra time. We don't think it's representative of the design's performance.

Initially, all three `FloatingPointPrinting_<type>_interpolated` tests regressed with the new design. We conformed these types to `TextOutputStreamable` and added a private ASCII-only fast path in `TextOutputStream`; this increased the performance of `Double` and `Float80` to be small improvements, but did little to help `Float`.

Benchmark code size slightly improved on average:

| Benchmark file                 | -O size improvement | -Osize size improvement |
| ------------------------------ | ------------------- | ----------------------- |
| StringInterpolation.o          | 1.18x               | 1.16x                   |
| FloatingPointPrinting.o        | 1.12x               | 1.11x                   |
| All files with notable changes | 1.02x               | 1.02x                   |

So did Swift library code size:

| Library                              | Size improvement |
| ------------------------------------ | ---------------- |
| libswiftSwiftPrivateLibcExtras.dylib | 1.20x            |
| libswiftFoundation.dylib             | 1.15x            |
| libswiftXCTest.dylib                 | 1.10x            |
| libswiftStdlibUnittest.dylib         | 1.06x            |
| libswiftCore.dylib.                  | 1.04x            |
| libswiftNetwork.dylib                | 1.02x            |
| libswiftSwiftOnoneSupport.dylib      | 1.02x            |
| libswiftsimd.dylib                   | 1.01x            |
| libswiftMetal.dylib                  | 0.90x            |
| libswiftSwiftReflectionTest.dylib    | 0.92x            |

We believe the current results already look pretty good, and further performance tuning is possible in the future. Other types can likely improve interpolation performance using `TextOutputStreamable`. Overall, this design has nowhere to go but up.

The default `init(stringLiteral:)` (which is only used for types implementing fully custom string interpolation) is currently about 0.5x the speed of a manually-implemented `init(stringLiteral:)`, but prototyping indicates that inlining certain fast paths from `String.reserveCapacity(_:)` and `String.append(_:)` can reduce that penalty to 0.93x, and we may be able to squeeze out gains beyond that. Even if we cannot close this gap completely, performance-sensitive types can always implement `init(stringLiteral:)` manually.

## Source compatibility

Since `ExpressibleByStringInterpolation` has been deprecated since Swift 3, we need not maintain source compatibility with existing conformances, nor do we propose preserving existing conformances to `ExpressibleByStringInterpolation` even in Swift 4 mode.

We do not propose preserving existing `init(stringInterpolation:)` or `init(stringInterpolationSegment:)` initializers, since they have always been documented as calls that should not be used directly. However, the source compatibility suite contains code that accidentally uses `init(stringInterpolationSegment:)` by writing `String.init` in a context expecting a `CustomStringConvertible` or `TextOutputStreamable` type. We have devised a set of overloads to `init(describing:)` that will match these accidental, implicit uses of `init(stringInterpolationSegment:)` without preserving explicit uses of `init(stringInterpolationSegment:)`.

We propose a set of `String.StringInterpolation.appendInterpolation` overloads that exactly match the current `init(stringInterpolationSegment:)` overloads, so "normal" interpolations will work exactly as before.

"Strange" interpolations like `\(x, y)` or `\(foo: x)`, which are currently accepted by the Swift compiler will be errors in Swift 5 mode. In Swift 4.2 mode, we will preserve the existing behavior with a warning; this means that Swift 4.2 code will only be able to use `appendInterpolation` overloads with a single unlabeled parameter, unless all other parameters have default values. Migration involves inserting an extra pair of parens or removing an argument label to preserve behavior.

## Effect on ABI stability

`ExpressibleByStringInterpolation` will need to be ABI-stable starting in Swift 5; we should adopt this proposal or some alternative and un-deprecate `ExpressibleByStringInterpolation` before that.

## Effect on API resilience

This API is pretty foundational and it would be difficult to change compatibly in the future.

## Alternatives considered

### Variadic-based designs

We considered several designs that, like the current design, passed segments to a variadic parameter. For example, we could wrap literal segments in `init(stringLiteral:)` instead of `init(stringInterpolationSegment:)` and otherwise keep the existing design:

```swift
String(stringInterpolation:
  String(stringLiteral: "hello "),
  String(stringInterpolationSegment: name),
  String(stringLiteral: "!"))
```

Or we could use an enum to differentiate literal segments from interpolated ones:

```swift
String(stringInterpolation:
  .literal("hello "),
  .interpolation(String.StringInterpolationType(name)),
  .literal("!"))
```

However, this requires that conformers expose a homogenous return value, which has expressibility and/or efficiency drawbacks. The proposed approach, which is statement based, keeps this as a detail internal to the conformer.

### Have a formal `appendInterpolation(_:)` requirement

We considered having a formal `appendInterpolation(_:)` requirement with an unconstrained generic parameter to mimic current behavior. We could even have a default implementation that vends strings and still honors overloading.

However, we would have to give up on conformers being able to restrict the types or interpolation segment forms permitted.

redpajama_set_name: RedPajamaGithub


New Characters For Re-vamp, now Updated to current RP standing's.
added new character, Reynardine - based off the fox spirit Reynardine from gunnerkrigg court.
Personality↔ a mixture of three sides, aggression, Justice and Kindness, one being with three sides of personality, Fate's own personality is governed by the three, leaving him with only confusion as to his own personality but on his own Fate is generally kind but usually questions everything against him.
Bio↔ sen-mithrarin "Fate", "he who is born of the Dust of others By Fate" created from the life thread its self, a living creature with a shattered soul, a soul made up of three, Fate exists through the wishes of others through the life thread after the sen-mithrarin before him passed on, Fate doesn't know who or what he is except for that he exists by the wishes of others but now where and who or time, little is known of him except for his three way shattered soul and his reason for being alive, the name "Fate" donned upon him for if it was not for the fate of others he would not exist, with his sides of his shattered soul come personality traits, a side effect or curse that make up his own being, Fate's Fragmented Soul known as "Jin" hinders his capable fighting ability and skill, leaving Fate to learn how to fight on his own, before the tavern event Fate had no sword of his own and proceeded to treat his wounds with what he could find, in his spare time to strengthen himself he would practice with the sword he found, using it as a means of exercise and physical recovery.
Cassius: occasional bursts of short temper, aggressive behavior towards enemies and friends alike and his displeasure for failure.
Dust: strong charisma, almost shy and is very reserved with good reason. This mannerism usually makes him come across as a bit stand-offish, Justice incarnated.
Jin: thoughtful towards people, labels his actions with reason, strong-willed, shows a great deal of consideration towards victims and offenders, Also hinders Fates fighting capability and skill growth.
Flaws↔ very limited to no Fighting skill/ability, needs training.
Special Abilities↔ Dust Storm: Rapidly spinning his blade in front of him, Fate creates a vacuum like vortex, that can push or pull objects around, large and or heavy objects are not effected, rapidly cuts close targets with wind attacks and blade strikes.
Weakness ↔ Jin: the soul of Jin hinders Fate's Fighting ability's, a noble soul without skill, without power.
Fears↔ Unknown at this time.
Extra↔ Fate has no memory and unlike the sen-mithrarin before him, he can't obtain/retain memory's of the souls that he has, Listed under "Traits" in red are the names of the three souls that make up Fate's own soul and what form of influence they have on him, Fate's own Shattered and Split soul is listed in Cyan, Fate's tail mainly helps him with his foot work and balance but can be used in a manner to grab something but not to hang from, pulling his tail also has no effect on him.
"is it by Fate that we meet"
"if your fate is at my hands, what path awaits you now?"
"if he was noble and pure of heart, and he was cold and malicious but not evil, but he was justice incarnate from the two, so what does that make me?"
Everyday I fight the colossuses in hope that one day I will find the one I love. Is she truly real or do I fight for a pointless cause. I fight looking For Awnser.
mia is rather blunt at most, but pretty straight forwards, she is disconnected from feelings of emotions and thinks little about it when she notice's it, nothing seems to surprise her but will create sarcastic comments at most, built into her coding is high levels of curiosity for odd objects and things to sinc with her anthropomorphic cat appearance, mia is usually quite helpful if not silent and may stand to protect others on a rare occasion, very rarely will mia show a caring side to other's or around them.
Bio↔ Mia, is a large humanoid anthromorphic cat with long rabbit like ears and a long tail. She is covered in bushy purple fur, green armor and wields a medium sized sword with a green blade that yields a paralysis effect should it draw blood, how she came to exist is unknown to her, mia's body is a holographic mechanical shell that can take severe damage before actual damage begins to show and weaken the avatar like body, major damage is calculated as deep cuts and wounds equal to what a human can withstand/die from where as minor damage is small cuts and burns, how ever inflicted injury's bleed and inflict a sense of pain which mia feels, the concept of her flawless giving her a more living look but a major flaw, her emerald green armor could possible be made of mythril metal's though its never actually been proven if it is mythril or just green colored steel, where as the blade of her sword is made of mythril and wields a paralysis poison.
though mia remembers her world which was an artificial word created as a game for humans mia some how ended up walking out of the Eostar Rift Portal from use of a chaos gate, in her world mia was considered a roaming AI what would ether aid others or watch them, commonly she traveled with a group of human players for no particular reason as she was not limited by law's or tasks.
Mia is able to temporary "die", time is required for her to Re-activate after receiving a killing blow, though limbs can be cut off, they in fact shatter into fragments as if glass, should mia's body completely shatter she can quickly reconstruct herself to a "living" state as long as the Echo cube is alive, her core dies and shatters as a new one is made from the echo cube at its location, should the echo cube be destroyed it requires a longer time for mia to reconstruct herself to a "living" state from the core that was in her own body.
"where there would be flesh and tissue every injury is hollow as it looks holographic and machine rather then living muscle and tissue, it all glows a bright olive like color as a glowing fluorescent liquid runs like blood dripping each injury, visibly from mia's injury's one can clearly see she is not a living creature..." this is because her body is a holographic shell that is also living, or at-least programmed to be, when sever blast damage is taken the "injured" area of her body may crack if not break and shatter leaving a clean hole, an example as the following.
Skill full with Heavy Blade and Short Blade's.
rest, drink and food not required.
"Mia is able to rebuild and/or Repair her self, and weapon."
"Mia's body is a holographic avatar like Shell but also mechanical giving the following benefits: ∞ Energy. +Natural Damage Resistance. Poison, Sickness and Disease Immunity"
"Mia is resourceful to others from her list of skills and use's."
"Mia is able to create a Distortion field around her as she launches half of her physical data in any given direction over a small distance (a form of evasive/offensive dash) projectiles/weapons pass through the Distortion ghost while the form is non-solid."
"the sword has the ability to infect a living target with a Paralysis inducing Poison should it draw blood upon attack's, the weak paralysis slows down the victims movements along with making them feel weaker and heavier, the more times struck the stronger the effects, non-lethal poison, only non-living and machines are immune to the effects."
Weakness ↔ Ranged Combat, Explosives, Lazor Weapons.
Extra↔ Emerald green armor believed to be Mythril but the armor is quite flexible and very sturdy/resistant, odd collar like item around the neck.
"curiosity didn't killed the cat, i killed 'that' cat."
"an abomination most machines are, i included, but at least i wont kill you."
the Echo cube is a talkative annoying Cube that doesn't know when to shut up, it tends to rattle and shake its self around on the ground to move and commonly when picked up but not wanted to be picked up.
it actually does speak and when it does it sound just like a portal turret.
from time to time the cube will be abused by mia for its annoying personality, though she needs it, mia wont actually attempt to damage it in any way, the cube how ever enjoys flying even if its picked up and thrown it can help but chant "wheee".
Talks, rattle's and bounce's around.
Beta Core: should Mia fall and her alpha Core dies, The Echo Cube creates a new core which allows Mia to reconstruct herself from the new Alpha Core.
Weakness ↔ Space and Fire.
Extra↔ its a Joke... but a use full item.
Personality ↔ Renard lives with regret each day, though he may be quite heartless not just metaphorically he is how ever quite the softy and once again not just methaphorically, how ever renard would kill if given the chance and a reason to do so and disrespects rules and orders given to him, His behaviour in large wolf form tends to be rather more mature than when in small wolf form, and tends to demonstrate greater diplomacy, levelheadedness, and mental acuity. Perhaps for this reason, in times of danger or stress, Renard typically will shift to his wolf form.
Bio ↔ Reynardine (self-titled Reynardine the Great), also known as Renard, is a fox-spirit with the ability to possess others' bodies, whether living or inanimate, his origins are a place known as Gillitie Wood, and is supposedly cousin to coyote mythos with a somewhat connection to The trickster figure known as Reynard the Fox though it is unknown exactly if this is the same Reynard, how ever he was named as Reynardine by Surma Carver the name is also the name of a demon steals the hearts of young girls though at the time reynard was oblivious to the illusion that fact he was being lured to the other side of the bridge rather then actually being courted with, this caused him to ask coyote for the power to possess body's, which died when he left them.
a few years later reynard tried to once again possess a body of a little girl to ensure his escape from the prison he was held with in after once again taking the body of an opponent he had defeated in battle, how ever she was tackled out of the way by another man and reynard ended up possessing wolf toy she had instead, though it is unknown if it was intended or an accident, as the girl owned the toy, she gained ownership over reynard and his actions and he was forced to do as she said by a contract which was made when he entered the toy, after a few years later reynard turned from his dark ways and grew fond of the wolf toy he possessed and "his master" though during a science experiment he was audience to the two were split apart when a tear in space and time was made and his very small light body was sucked into the tear splitting the two apart, Reynard now looks for a way back home.
Flaws ↔ too many to list for just a toy.
Reynardine is capable of manipulating his body to a variety of forms should he possess an inanimate such as a wolf toy. Initially, more anthropomorphic proportions and features or by taking on the appearance of a white wolf. To a lesser degree, Renard also demonstrate's this ability by lacing and unlacing the stitching of his arm in order to utilize a set of lockpicks stored there when in Plush form for picking lock's.
those who are able to see spirits on a different plane of existence such as through or in the spirit world will have the ability to see Reynardine's true appearance, though he exists only as a spirit until he leaves what ever body he is in possession of and returns to his own body.
when a living body is possessed the host can't think or feel anything, but they aren't quite dead, how ever they can not regain control or be communicated to in anyway or form, even by Renard, but any body (immortal/inanimate excluded) that is possessed by Reynardine dies once he leaves the body, immortal being's may be unconscious for an few long minutes after renard leaves their body. inanimate objects like toys are unaffected what so ever, he also can possess any inanimate object as long as it has eye's even if their drawn on, his sensors rely on what ever the object has, eg mouth, nose and ears.
if an object belongs to someone, they gain full control/ownership of Renard and the previous ownership shifts, existing orders are no longer void.
Way of life ↔ Reynardine can be many things and is seen differently by others but what people make of him he lets them decide while he just acts himself.